[GitHub] flink pull request #4468: [FLINK-7347] [streaming] Keep ids for current chec...
Github user ymost closed the pull request at: https://github.com/apache/flink/pull/4468 --- 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. ---
[GitHub] flink issue #4468: [FLINK-7347] [streaming] Keep ids for current checkpoint ...
Github user ymost commented on the issue: https://github.com/apache/flink/pull/4468 Thanks for merging! --- 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. ---
[GitHub] flink issue #4150: [FLINK-6951] Incompatible versions of httpcomponents jars...
Github user burkaygur commented on the issue: https://github.com/apache/flink/pull/4150 similar to @bowenli86 i am receiving the same socket error. Tried the proposed fix in the PR, but still getting the error. Bumped the JDK version, didnt help either. Anyone has a working configuration for this connector? --- 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. ---
[jira] [Commented] (FLINK-7269) Refactor passing of dynamic properties
[
https://issues.apache.org/jira/browse/FLINK-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134148#comment-16134148
]
ASF GitHub Bot commented on FLINK-7269:
---
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/4415
Thanks for your work @zjureel and sorry that it took me so long to get back
to you. Will be merging your PR now.
> Refactor passing of dynamic properties
> --
>
> Key: FLINK-7269
> URL: https://issues.apache.org/jira/browse/FLINK-7269
> Project: Flink
> Issue Type: Improvement
> Components: Configuration
>Affects Versions: 1.3.1
>Reporter: Till Rohrmann
>Assignee: Fang Yong
>
> In order to set dynamic properties when loading the {{Configuration}} via
> {{GlobalConfiguration.loadConfiguration}}, we currently set a static field in
> {{GlobalConfiguration}} which is read whenever we load the {{Configuration}}.
> I think this is not a good pattern I propose to remove this functionality.
> Instead we should explicitly add the dynamic properties to the loaded
> {{Configuration}} at start of the application.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] flink issue #4415: [FLINK-7269] Refactor passing of dynamic properties
Github user tillrohrmann commented on the issue: https://github.com/apache/flink/pull/4415 Thanks for your work @zjureel and sorry that it took me so long to get back to you. Will be merging your PR now. --- 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. ---
[jira] [Commented] (FLINK-7077) Implement task release to support dynamic scaling
[
https://issues.apache.org/jira/browse/FLINK-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134146#comment-16134146
]
ASF GitHub Bot commented on FLINK-7077:
---
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/4560
> Implement task release to support dynamic scaling
> -
>
> Key: FLINK-7077
> URL: https://issues.apache.org/jira/browse/FLINK-7077
> Project: Flink
> Issue Type: Sub-task
> Components: Mesos, ResourceManager
>Reporter: Till Rohrmann
>Assignee: Eron Wright
> Fix For: 1.4.0
>
>
> In order to support dynamic scaling, the {{MesosResourceManager}} has to be
> able to release Mesos tasks. We have to implement
> {{MesosResourceManager#stopWorker}} for that.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (FLINK-7077) Implement task release to support dynamic scaling
[
https://issues.apache.org/jira/browse/FLINK-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-7077.
Resolution: Fixed
Assignee: Eron Wright
Fix Version/s: 1.4.0
Added via 40656c5dfdab7c0a1a7794dfe3a5f661f6156c6f
> Implement task release to support dynamic scaling
> -
>
> Key: FLINK-7077
> URL: https://issues.apache.org/jira/browse/FLINK-7077
> Project: Flink
> Issue Type: Sub-task
> Components: Mesos, ResourceManager
>Reporter: Till Rohrmann
>Assignee: Eron Wright
> Fix For: 1.4.0
>
>
> In order to support dynamic scaling, the {{MesosResourceManager}} has to be
> able to release Mesos tasks. We have to implement
> {{MesosResourceManager#stopWorker}} for that.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] flink pull request #4560: Flink 7077
Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/4560 --- 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. ---
[jira] [Commented] (FLINK-7300) End-to-end tests are instable on Travis
[
https://issues.apache.org/jira/browse/FLINK-7300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134144#comment-16134144
]
Till Rohrmann commented on FLINK-7300:
--
{{AskTimeoutException}} can easily occur in a real life scenario without
something being broken. These exceptions should then only be logged on warn
level and not error, right?
I think we should harden the test such that we don't have false positives. To
me this sounds a bit like that our verification of a successful test run (e.g.
no exception in the log) is broken and should be changed. It could also be the
case that we log exceptions which shouldn't be logged because they are just
misleading.
> End-to-end tests are instable on Travis
> ---
>
> Key: FLINK-7300
> URL: https://issues.apache.org/jira/browse/FLINK-7300
> Project: Flink
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.4.0
>Reporter: Tzu-Li (Gordon) Tai
>Assignee: Aljoscha Krettek
> Labels: test-stability
> Fix For: 1.4.0
>
>
> It seems like the end-to-end tests are instable, causing the {{misc}} build
> profile to sporadically fail.
> Incorrect matched output:
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/258569408/log.txt?X-Amz-Expires=30=20170731T060526Z=AWS4-HMAC-SHA256=AKIAJRYRXRSVGNKPKO5A/20170731/us-east-1/s3/aws4_request=host=4ef9ff5e60fe06db53a84be8d73775a46cb595a8caeb806b05dbbf824d3b69e8
> Another failure example of a different cause then the above, also on the
> end-to-end tests:
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/258841693/log.txt?X-Amz-Expires=30=20170731T060007Z=AWS4-HMAC-SHA256=AKIAJRYRXRSVGNKPKO5A/20170731/us-east-1/s3/aws4_request=host=4a106b3990228b7628c250cc15407bc2c131c8332e1a94ad68d649fe8d32d726
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (FLINK-6630) Implement FLIP-6 MesosAppMasterRunner
[ https://issues.apache.org/jira/browse/FLINK-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134141#comment-16134141 ] ASF GitHub Bot commented on FLINK-6630: --- Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/4555 > Implement FLIP-6 MesosAppMasterRunner > - > > Key: FLINK-6630 > URL: https://issues.apache.org/jira/browse/FLINK-6630 > Project: Flink > Issue Type: Sub-task > Components: Mesos >Reporter: Eron Wright >Assignee: Eron Wright > Fix For: 1.4.0 > > > A new runner must be developed for the FLIP-6 RM. Target the "single job" > scenario. > Take some time to consider a general solution or a base implementation that > is shared with the old implementation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] flink pull request #4555: [FLINK-6630] [Mesos] Implement FLIP-6 MesosAppMast...
Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/4555 --- 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. ---
[jira] [Resolved] (FLINK-6630) Implement FLIP-6 MesosAppMasterRunner
[ https://issues.apache.org/jira/browse/FLINK-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Till Rohrmann resolved FLINK-6630. -- Resolution: Fixed Fix Version/s: 1.4.0 Added via bbac4a6c922199db08a5244d0fa1262a5f16d479 > Implement FLIP-6 MesosAppMasterRunner > - > > Key: FLINK-6630 > URL: https://issues.apache.org/jira/browse/FLINK-6630 > Project: Flink > Issue Type: Sub-task > Components: Mesos >Reporter: Eron Wright >Assignee: Eron Wright > Fix For: 1.4.0 > > > A new runner must be developed for the FLIP-6 RM. Target the "single job" > scenario. > Take some time to consider a general solution or a base implementation that > is shared with the old implementation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (FLINK-6631) Implement FLIP-6 MesosTaskExecutorRunner
[ https://issues.apache.org/jira/browse/FLINK-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Till Rohrmann resolved FLINK-6631. -- Resolution: Fixed Assignee: Eron Wright Fix Version/s: 1.4.0 Added via bbac4a6c922199db08a5244d0fa1262a5f16d479 > Implement FLIP-6 MesosTaskExecutorRunner > > > Key: FLINK-6631 > URL: https://issues.apache.org/jira/browse/FLINK-6631 > Project: Flink > Issue Type: Sub-task > Components: Mesos >Reporter: Eron Wright >Assignee: Eron Wright > Fix For: 1.4.0 > > > Develop a Mesos task executor runner. As with FLINK-6630, consider a > general solution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FLINK-7463) Release nascent workers on slot request timeout
[ https://issues.apache.org/jira/browse/FLINK-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134130#comment-16134130 ] Till Rohrmann commented on FLINK-7463: -- I think this is not only a subtask of the Flink on Mesos integration but applies to Yarn as well. Maybe we can convert this into an issue. > Release nascent workers on slot request timeout > > > Key: FLINK-7463 > URL: https://issues.apache.org/jira/browse/FLINK-7463 > Project: Flink > Issue Type: Sub-task > Components: Mesos >Reporter: Eron Wright > > A slot request causes a new worker to be allocated. If the slot request > times out or is cancelled before the worker is launched, cancel the worker > request if possible. > This is an optimization because an idle slot is eventually released anyway. > However, I observe that a lot of worker requests pile up in the launch > coordinator, as the JM keeps making request after request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FLINK-6630) Implement FLIP-6 MesosAppMasterRunner
[ https://issues.apache.org/jira/browse/FLINK-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134126#comment-16134126 ] ASF GitHub Bot commented on FLINK-6630: --- Github user tillrohrmann commented on the issue: https://github.com/apache/flink/pull/4555 Merging this PR. > Implement FLIP-6 MesosAppMasterRunner > - > > Key: FLINK-6630 > URL: https://issues.apache.org/jira/browse/FLINK-6630 > Project: Flink > Issue Type: Sub-task > Components: Mesos >Reporter: Eron Wright >Assignee: Eron Wright > > A new runner must be developed for the FLIP-6 RM. Target the "single job" > scenario. > Take some time to consider a general solution or a base implementation that > is shared with the old implementation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] flink issue #4555: [FLINK-6630] [Mesos] Implement FLIP-6 MesosAppMasterRunne...
Github user tillrohrmann commented on the issue: https://github.com/apache/flink/pull/4555 Merging this PR. --- 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. ---
[jira] [Commented] (FLINK-5486) Lack of synchronization in BucketingSink#handleRestoredBucketState()
[
https://issues.apache.org/jira/browse/FLINK-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134044#comment-16134044
]
ASF GitHub Bot commented on FLINK-5486:
---
Github user zhangminglei commented on the issue:
https://github.com/apache/flink/pull/4356
triggering now
> Lack of synchronization in BucketingSink#handleRestoredBucketState()
>
>
> Key: FLINK-5486
> URL: https://issues.apache.org/jira/browse/FLINK-5486
> Project: Flink
> Issue Type: Bug
> Components: Streaming Connectors
>Reporter: Ted Yu
>Assignee: mingleizhang
> Fix For: 1.3.3
>
>
> Here is related code:
> {code}
>
> handlePendingFilesForPreviousCheckpoints(bucketState.pendingFilesPerCheckpoint);
> synchronized (bucketState.pendingFilesPerCheckpoint) {
> bucketState.pendingFilesPerCheckpoint.clear();
> }
> {code}
> The handlePendingFilesForPreviousCheckpoints() call should be enclosed inside
> the synchronization block. Otherwise during the processing of
> handlePendingFilesForPreviousCheckpoints(), some entries of the map may be
> cleared.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] flink issue #4356: [FLINK-5486] Fix lacking of synchronization in BucketingS...
Github user zhangminglei commented on the issue: https://github.com/apache/flink/pull/4356 triggering now --- 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. ---
