Github user DarkKnightCZ closed the pull request at:
https://github.com/apache/flink/pull/609
---
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
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/609#issuecomment-97424107
@DarkKnightCZ, only you can close the PR. Could you do so?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user DarkKnightCZ commented on the pull request:
https://github.com/apache/flink/pull/609#issuecomment-96182670
@StephanEwen: Hi, yes, you're correct. In 0.9 it works as it should (i.e.
tries connecting to JM several times)
So i guess this PR can be closed
---
If your
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/609#issuecomment-94916699
Forwarding comments from JIRA:
I think @DarkKnightCZ is using versiob 0.8.x and Till Rohrmann is talking
about 0.9
The startup is handled very differently
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/609#issuecomment-94581541
@DarkKnightCZ that sounds strange. The TM should not terminate itself if it
cannot connect to the JM unless the maximum registration duration has been
configured. Is
Github user DarkKnightCZ commented on a diff in the pull request:
https://github.com/apache/flink/pull/609#discussion_r28688289
--- Diff: flink-dist/src/main/flink-bin/bin/start-cluster.sh ---
@@ -37,6 +37,26 @@ fi
# cluster mode, bring up job manager locally and a task manager
Github user DarkKnightCZ commented on the pull request:
https://github.com/apache/flink/pull/609#issuecomment-94451193
@tillrohrmann
The problem that occurred was that JM bound the IP:PORT with some delay, so
TMs failed to start, since they couldn't connect.
When i tried
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/609#issuecomment-9159
As far as I understood it, the goal of the change is to wait until the JM
has been started before starting the TMs.
So the TMs would not start if the JM failed to star
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/609#issuecomment-9121
The TaskManager's maximum registration duration is configured by the config
value ```taskmanager.maxRegistrationDuration```. The default value is set to
infinity for
Github user rmetzger commented on a diff in the pull request:
https://github.com/apache/flink/pull/609#discussion_r28685121
--- Diff: flink-dist/src/main/flink-bin/bin/start-cluster.sh ---
@@ -37,6 +37,26 @@ fi
# cluster mode, bring up job manager locally and a task manager on
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/609#issuecomment-94442619
The TaskManager uses an exponential backoff strategy to resolve connection
problems with the JobManager.
On Mon, Apr 20, 2015 at 11:07 AM, Max wrote:
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/609#issuecomment-94401080
Thanks for the pull request. Seems to work fine. I was wondering, shouldn't
the task managers repeatably try to build up a connection to the job manager?
For me, that seems to
GitHub user DarkKnightCZ opened a pull request:
https://github.com/apache/flink/pull/609
[FLINK-1908] JobManager startup delay isn't considered when using
start-cluster.sh script
Creates dependency on netcat package (nc)
You can merge this pull request into a Git repository by runn
13 matches
Mail list logo
