Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/328#issuecomment-71002640
You are right @hsaputra, because I'm not sure which approach is the best.
In the corresponding JIRA issue I have tried to give a summary of what I think
are the pros and cons of indefinitely many registration tries vs. a limited
number of tries and a constant pause in between tries vs. an increasing pause.
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
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
---
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.
---
