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 Tue, 19 Jul 2016 12:23:27 GMT
Github user tillrohrmann commented on the issue:

    https://github.com/apache/flink/pull/2257
  
    I think by imposing this contract we actually introduced problems we didn't have before.
Thus, in order to remedy these problems for the upcoming release and go back a bit in the
direction of the pre-RM age, I loosened the contract of the RM so that it can no longer reject
TM registrations. This makes sense in my opinion, since we don't have a mean to shut down
orphaned TMs anyway.
    
    So in this version, the RM's task is to ensure that at least a predefined set of resources
is allocated and to notify the JM about a TM death (not strictly mandatory).
    
    What we could actually do is to also register orphaned TMs (or ones registered by a different
RM). Then we wouldn't have the problem that we allocate too many resources for a JM.


---
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.
---

Mime
View raw message