You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by tillrohrmann <gi...@git.apache.org> on 2015/06/16 14:41:23 UTC
[GitHub] flink pull request: [FLINK-2225] [scheduler] Excludes static code ...
GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/843
[FLINK-2225] [scheduler] Excludes static code paths from co-location constraint to avoid scheduling problems
Including static code paths in the co-location constraints can lead to a slot assignment for the co-location constraints which is not satisfiable.
This can be caused by a subsequent execution of the static code tasks on the same TM. Then all the following co-located tasks have to be deployed in the same slots. When you have an iteration whose tasks have to be run all simultaneously, then this will lead to an unsatisfiable scheduling case.
The solution is to exclude static code paths from the co-location groups.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/flink fixCC
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/843.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 #843
----
commit 9e897c681171116518a7a66a08e9a10350339d8a
Author: Till Rohrmann <tr...@apache.org>
Date: 2015-06-16T10:27:02Z
[FLINK-2225] [scheduler] Excludes static code paths from co-location constraint to avoid scheduling problems
----
---
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: [FLINK-2225] [scheduler] Excludes static code ...
Posted by tillrohrmann <gi...@git.apache.org>.
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/843#issuecomment-112496491
Will merge it then.
---
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: [FLINK-2225] [scheduler] Excludes static code ...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/843
---
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: [FLINK-2225] [scheduler] Excludes static code ...
Posted by StephanEwen <gi...@git.apache.org>.
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/843#issuecomment-112494219
Great catch!
+1 to merge
---
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: [FLINK-2225] [scheduler] Excludes static code ...
Posted by tillrohrmann <gi...@git.apache.org>.
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/843#issuecomment-112410790
@StephanEwen do I overlook something by excluding static code paths from the co-location groups?
---
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.
---