You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by mxm <gi...@git.apache.org> on 2016/06/30 16:51:01 UTC
[GitHub] flink pull request #2189: [FLINK-3667] delay connection to JobManager until ...
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/2189
[FLINK-3667] delay connection to JobManager until job execution
- lazily initialize ActorSystem
- make sure it is not created before job execution
- print connection information on the CLI
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink lazy-init
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2189.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 #2189
----
----
---
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.
---
[GitHub] flink issue #2189: [FLINK-3667] delay connection to JobManager until job exe...
Posted by mxm <gi...@git.apache.org>.
Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2189
Sorry, didn't see your comments. The test failures should be resolved (I ran `mvn verify`).
The changes delay the creation of the ActorSystem and thus any blocking actions until we have executed the user jar.
---
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.
---
[GitHub] flink pull request #2189: [FLINK-3667] delay connection to JobManager until ...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/2189
---
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.
---
[GitHub] flink issue #2189: [FLINK-3667] delay connection to JobManager until job exe...
Posted by zentol <gi...@git.apache.org>.
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/2189
Please provide some context for this PR, the referenced JIRA is marked as closed.
---
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.
---
[GitHub] flink issue #2189: [FLINK-3667] delay connection to JobManager until job exe...
Posted by zentol <gi...@git.apache.org>.
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/2189
there are also some test failures in flink-clients:
```
testManualOptionsOverridesConfig(org.apache.flink.client.CliFrontendAddressConfigurationTest) Time elapsed: 0.031 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<[ip-10-221-130-22.ec2.internal]> but was:<[10.221.130.22]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at org.apache.flink.client.CliFrontendTestUtils.checkJobManagerAddress(CliFrontendTestUtils.java:110)
at org.apache.flink.client.CliFrontendAddressConfigurationTest.testManualOptionsOverridesConfig(CliFrontendAddressConfigurationTest.java:99)
```
---
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.
---