Github user uce commented on the pull request:
https://github.com/apache/flink/pull/328#issuecomment-71003641
Thanks for the summary, Till :)
On 22 Jan 2015, at 11:48, Till Rohrmann <[email protected]> wrote:
> Indefinitely many registration tries:
> Pros: If the JobManager becomes available at some point in time, then the
TaskManager will definitely connect to it
> Cons: If the JobManager dies of some reason, then the TaskManager will
linger around for all eternity or until it is stopped manually
I am against this as the lingering around is imo problematic.
> Limited number of tries:
> Pros: Will terminate itself after some time
> Cons: The time interval might be too short for the JobManager to get
started
>
> Constant pause:
> Pros: Relatively quick response time
> Cons: Causing network traffic until the JobManager has been started
>
> Increasing pause:
> Pros: Reduction of network traffic if the JobManager takes a little bit
longer to start
> Cons: Might delay the registration process if one interval was just missed
Maybe keep the current strategy (n times constant pause c) and then start
backing off?
Has this been reported as a problem in a setup? Since this is not very
complicated, but it's hard to find a heuristic to match all use cases, we might
just implement all strategies, keep the current as default and make it
configurable.=
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
