You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@flink.apache.org by Hao Sun <ha...@zendesk.com> on 2017/12/01 22:14:44 UTC
non-shared TaskManager-specific config file
Hi team, I am wondering how can I create a non-shared config file and let
Flink read it. Can I use include in the config? Or I have to prepare a
different config for each TM?
https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/config.html
-
taskmanager.hostname: The hostname of the network interface that the
TaskManager binds to. By default, the TaskManager searches for network
interfaces that can connect to the JobManager and other TaskManagers. This
option can be used to define a hostname if that strategy fails for some
reason. Because different TaskManagers need different values for this
option, it usually is specified in an additional non-shared
TaskManager-specific config file.
Re: non-shared TaskManager-specific config file
Posted by Hao Sun <ha...@zendesk.com>.
https://issues.apache.org/jira/browse/FLINK-8197, here is the JIRA link for
xref.
On Mon, Dec 4, 2017 at 7:35 AM Hao Sun <ha...@zendesk.com> wrote:
> Sure, I will do that.
>
> On Mon, Dec 4, 2017, 07:26 Fabian Hueske <fh...@gmail.com> wrote:
>
>> Can you create a JIRA issue to propose the feature?
>>
>> Thank you,
>> Fabian
>>
>> 2017-12-04 16:15 GMT+01:00 Hao Sun <ha...@zendesk.com>:
>>
>>> Thanks. If we can support include configuration dir that will be very
>>> helpful.
>>>
>>> On Mon, Dec 4, 2017, 00:50 Chesnay Schepler <ch...@apache.org> wrote:
>>>
>>>> You will have to create a separate config for each TaskManager.
>>>>
>>>>
>>>> On 01.12.2017 23:14, Hao Sun wrote:
>>>>
>>>> Hi team, I am wondering how can I create a non-shared config file and
>>>> let Flink read it. Can I use include in the config? Or I have to prepare a
>>>> different config for each TM?
>>>>
>>>>
>>>> https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/config.html
>>>> <https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/config.html>
>>>>
>>>>
>>>> -
>>>>
>>>> taskmanager.hostname: The hostname of the network interface that
>>>> the TaskManager binds to. By default, the TaskManager searches for network
>>>> interfaces that can connect to the JobManager and other TaskManagers. This
>>>> option can be used to define a hostname if that strategy fails for some
>>>> reason. Because different TaskManagers need different values for this
>>>> option, it usually is specified in an additional non-shared
>>>> TaskManager-specific config file.
>>>>
>>>>
>>>>
>>>>
>>
Re: non-shared TaskManager-specific config file
Posted by Hao Sun <ha...@zendesk.com>.
Sure, I will do that.
On Mon, Dec 4, 2017, 07:26 Fabian Hueske <fh...@gmail.com> wrote:
> Can you create a JIRA issue to propose the feature?
>
> Thank you,
> Fabian
>
> 2017-12-04 16:15 GMT+01:00 Hao Sun <ha...@zendesk.com>:
>
>> Thanks. If we can support include configuration dir that will be very
>> helpful.
>>
>> On Mon, Dec 4, 2017, 00:50 Chesnay Schepler <ch...@apache.org> wrote:
>>
>>> You will have to create a separate config for each TaskManager.
>>>
>>>
>>> On 01.12.2017 23:14, Hao Sun wrote:
>>>
>>> Hi team, I am wondering how can I create a non-shared config file and
>>> let Flink read it. Can I use include in the config? Or I have to prepare a
>>> different config for each TM?
>>>
>>>
>>> https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/config.html
>>> <https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/config.html>
>>>
>>>
>>> -
>>>
>>> taskmanager.hostname: The hostname of the network interface that the
>>> TaskManager binds to. By default, the TaskManager searches for network
>>> interfaces that can connect to the JobManager and other TaskManagers. This
>>> option can be used to define a hostname if that strategy fails for some
>>> reason. Because different TaskManagers need different values for this
>>> option, it usually is specified in an additional non-shared
>>> TaskManager-specific config file.
>>>
>>>
>>>
>>>
>
Re: non-shared TaskManager-specific config file
Posted by Fabian Hueske <fh...@gmail.com>.
Can you create a JIRA issue to propose the feature?
Thank you,
Fabian
2017-12-04 16:15 GMT+01:00 Hao Sun <ha...@zendesk.com>:
> Thanks. If we can support include configuration dir that will be very
> helpful.
>
> On Mon, Dec 4, 2017, 00:50 Chesnay Schepler <ch...@apache.org> wrote:
>
>> You will have to create a separate config for each TaskManager.
>>
>>
>> On 01.12.2017 23:14, Hao Sun wrote:
>>
>> Hi team, I am wondering how can I create a non-shared config file and let
>> Flink read it. Can I use include in the config? Or I have to prepare a
>> different config for each TM?
>>
>> https://ci.apache.org/projects/flink/flink-docs-
>> release-1.3/setup/config.html
>>
>>
>> -
>>
>> taskmanager.hostname: The hostname of the network interface that the
>> TaskManager binds to. By default, the TaskManager searches for network
>> interfaces that can connect to the JobManager and other TaskManagers. This
>> option can be used to define a hostname if that strategy fails for some
>> reason. Because different TaskManagers need different values for this
>> option, it usually is specified in an additional non-shared
>> TaskManager-specific config file.
>>
>>
>>
>>
Re: non-shared TaskManager-specific config file
Posted by Hao Sun <ha...@zendesk.com>.
Thanks. If we can support include configuration dir that will be very
helpful.
On Mon, Dec 4, 2017, 00:50 Chesnay Schepler <ch...@apache.org> wrote:
> You will have to create a separate config for each TaskManager.
>
>
> On 01.12.2017 23:14, Hao Sun wrote:
>
> Hi team, I am wondering how can I create a non-shared config file and let
> Flink read it. Can I use include in the config? Or I have to prepare a
> different config for each TM?
>
>
> https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/config.html
> <https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/config.html>
>
>
> -
>
> taskmanager.hostname: The hostname of the network interface that the
> TaskManager binds to. By default, the TaskManager searches for network
> interfaces that can connect to the JobManager and other TaskManagers. This
> option can be used to define a hostname if that strategy fails for some
> reason. Because different TaskManagers need different values for this
> option, it usually is specified in an additional non-shared
> TaskManager-specific config file.
>
>
>
>
Re: non-shared TaskManager-specific config file
Posted by Chesnay Schepler <ch...@apache.org>.
You will have to create a separate config for each TaskManager.
On 01.12.2017 23:14, Hao Sun wrote:
> Hi team, I am wondering how can I create a non-shared config file and
> let Flink read it. Can I use include in the config? Or I have to
> prepare a different config for each TM?
>
> https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/config.html
>
> *
>
> |taskmanager.hostname|: The hostname of the network interface that
> the TaskManager binds to. By default, the TaskManager searches for
> network interfaces that can connect to the JobManager and other
> TaskManagers. This option can be used to define a hostname if that
> strategy fails for some reason. Because different TaskManagers
> need different values for this option, it usually is specified in
> an additional non-shared TaskManager-specific config file.
>
>