flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tillrohrmann <...@git.apache.org>
Subject [GitHub] flink issue #2257: [FLINK-4152] Allow re-registration of TMs at resource man...
Date Wed, 20 Jul 2016 11:41:18 GMT
Github user tillrohrmann commented on the issue:

    Hi @mxm, I've changed the implementation such that we no longer need the `containersLaunched`
map in the `YarnFlinkResourceManager`. Instead we're not clearing the `registeredWorkers`
map in the `FlinkResourceManager` when the `JobManager` loses leadership. Thus, the `registeredWorkers`
field denotes the successfully started task managers (and the containers they are running
    Additionally I reintroduced the reconnect resource manager functionality in the job manager.
This should make sure that the resource manager is eventually notified about newly registered
resources. In the current implementation, however, the resource manager will always accept
the register resource messages. So only if the message gets lost and thus triggers a timeout
exception, the reconnect resource manager message is sent.
    Would be great if you could take another look at the changes.

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 infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message