Dear flink community,
First I need provide some minimum information about my deployment scenario: I'm running application inside of Flink docker, below original Dockerfile: ----------------------------------------------------------------------------------------------------------- FROM flink:1.13.0-scala_2.11-java11 ------------------------------------------------------------------------------------------------------------------------------- If we will ignore irrelevant parts of Dockerfile, the only 2 things remains ( beside FROM statement) 1. Overwritten flink-conf.yml + slaves 2. CMD which executes start-cluster and job. My flink-conf.yml: --------------------------------------------------------------------------------------------------------- rest.address: localhost
Slaves file contain single line with localhost. After start of docker, I noticed that application doesn't work due lack of slots. When I checked flink-conf.yml I noticed that taskmanager.numberOfTaskSlots is set to 1. P.S. during first time, daemon.sh complained that it doesn't have write permissions to change flink-conf.yml, when I added chown flink.flink /opt/flink/flink-conf.yml - it stopped to complain & taskmanager.numberOfTaskSlots change occured. Any suggestions ? Best regards, Alexander |
I believe this is due to FLINK-21037;
we did not consider the possibility of users mounting the
configuration directly, and instead assumed that modifications to
the config always go through the FLINK_PROPERTIES environment
variable.
That would also be the workaround for
your issue.
On 5/12/2021 2:06 PM, Alex Drobinsky
wrote:
|
You could also configure the number of
slots via the TASK_MANAGER_NUMBER_OF_TASK_SLOTS
environment variable.
On 5/12/2021 2:19 PM, Chesnay Schepler
wrote:
|
Thanks a lot ! I used TASK_MANAGER_NUMBER_OF_TASK_SLOTS in my docker-compose.yml, it works perfectly :) In which format I could provide parameters via FLINK_PROPERTIES ? I'm thinking of abandoning the idea to copy flink-conf in Dockerfile. Is it limited to a specific set of parameters or generic ? ср, 12 мая 2021 г. в 15:20, Chesnay Schepler <[hidden email]>:
|
The contents of FLINK_PROPERTIES are piped as-is into the flink
configuration, and thus require the same format as the
configuration. On 5/12/2021 2:36 PM, Alex Drobinsky
wrote:
|
If flink-conf.yaml is readonly, flink will complain but work fine?
From: Chesnay Schepler <[hidden email]>
Sent: Wednesday, May 12, 2021 5:38 AM To: Alex Drobinsky <[hidden email]> Cc: [hidden email] <[hidden email]> Subject: Re: After upgrade from 1.11.2 to 1.13.0 parameter taskmanager.numberOfTaskSlots set to 1. The contents of FLINK_PROPERTIES are piped as-is into the flink configuration, and thus require the same format as the configuration. On 5/12/2021 2:36 PM, Alex Drobinsky wrote:
|
Free forum by Nabble | Edit this page |