GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/2450
[Flink-4458] Replace ForkableFlinkMiniCluster by LocalFlinkMiniCluster
This PR is based on #2449. Thus, only the commits 5a2c70f and e07ad44 are
relevant.
The PR refactors the `LocalFlinkMiniCluster` and the `TestingCluster` so
that they can replace the `ForkableFlinkMiniCluster`. The
`LocalFlinkMiniCluster` now starts all distributed components under a random
port. This is possible with #2449.
The difference of the `TestingCluster` compared to the
`LocalFlinkMiniCluster` is that it starts the testing components (e.g.
`TestingJobManager`, `TestingTaskManager`, etc.) instead of the plain ones. It
also allows to start the `JobManager` in a synchronous mode. Furthermore, it
offers some operations like restarting the leading `JobManager` under the same
port.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/flink FLINK-4458
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2450.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 #2450
----
commit 96b1772d4581365eeec6614827b36f76a83ba5d0
Author: Till Rohrmann <[email protected]>
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.
commit 5a2c70fccfc480d777788b2697af3cd0eaf149a2
Author: Till Rohrmann <[email protected]>
Date: 2016-08-31T15:58:09Z
[FLINK-4458] Refactored LocalFlinkMiniCluster and TestingCluster
commit e07ad443421edba93bcb3ac7831909b6fd012a51
Author: Till Rohrmann <[email protected]>
Date: 2016-08-31T16:25:07Z
[FLINK-4458] Replace ForkableFlinkMiniCluster by LocalFlinkMiniCluster
Add RequestNumActiveConnections and RequestBroadcastVariablesWithReferences
to TaskManager
----
---
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.
---