GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/2449
[FLINK-4455] [FLINK-4424] [networkenv] Make NetworkEnvironment independent
of ActorGateway and JobManager association
Makes the NetworkEnvironment independent of the JobManager association.
This means that the
NetworkEnvironment and with it the ConnectionManager is started before the
TaskManager actor
is executed. Furthermore, the ConnectionManager keeps running even in case
of a JobManager
disassocation. In the wake of the remodelling this behaviour, the
PartitionStateChecker and
the ResultPartitionConsumableNotifier which depend on the JobManager
association were moved
out of the NetworkEnvironment. They are now contained in the
SlotEnvironment which will be
set up when the TaskManager connects to a JobManager. The SlotEnvironment
contains all
information related to the associated JobManager. Since all slots are
implicitly associated
with the JobManager which is the leader, we only create one SlotEnvironment
which is shared
by all Tasks.
Introduce SlotEnvironment to accommodate the PartitionStateChecker and
ResultPartitionConsumableNotifier
Remove the PartitionStateChecker and the ResultPartitionConsumableNotifier
from the
NetworkEnvironment. Start the NetworkEnvironment when the TaskManager
components are
created. Keep the NetworkEnvironment running also when the JobManager is
disassociated.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/flink FLINK-4455
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2449.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2449
----
commit 96b1772d4581365eeec6614827b36f76a83ba5d0
Author: Till Rohrmann <trohrm...@apache.org>
Date: 2016-08-31T07:33:46Z
[FLINK-4455] [FLINK-4424] [networkenv] Make NetworkEnvironment independent
of ActorGateway and JobManager association
Makes the NetworkEnvironment independent of the JobManager association.
This means that the
NetworkEnvironment and with it the ConnectionManager is started before the
TaskManager actor
is executed. Furthermore, the ConnectionManager keeps running even in case
of a JobManager
disassocation. In the wake of the remodelling this behaviour, the
PartitionStateChecker and
the ResultPartitionConsumableNotifier which depend on the JobManager
association were moved
out of the NetworkEnvironment. They are now contained in the
SlotEnvironment which will be
set up when the TaskManager connects to a JobManager. The SlotEnvironment
contains all
information related to the associated JobManager. Since all slots are
implicitly associated
with the JobManager which is the leader, we only create one SlotEnvironment
which is shared
by all Tasks.
Introduce SlotEnvironment to accommodate the PartitionStateChecker and
ResultPartitionConsumableNotifier
Remove the PartitionStateChecker and the ResultPartitionConsumableNotifier
from the
NetworkEnvironment. Start the NetworkEnvironment when the TaskManager
components are
created. Keep the NetworkEnvironment running also when the JobManager is
disassociated.
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
