[jira] [Commented] (FLINK-22761) Cannot remove POJO fields

[ https://issues.apache.org/jira/browse/FLINK-22761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528451#comment-17528451 ] Scott Kidder commented on FLINK-22761: -- This is a duplicate of FLINK-21752 > Cannot remove POJO

[jira] [Commented] (FLINK-13111) FlinkKinesisConsumer fails with endpoint and region used together

[ https://issues.apache.org/jira/browse/FLINK-13111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16912792#comment-16912792 ] Scott Kidder commented on FLINK-13111: -- This has been addressed by a PR I submitted earlier this

[jira] [Closed] (FLINK-9127) Filesystem State Backend logged incorrectly

[ https://issues.apache.org/jira/browse/FLINK-9127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder closed FLINK-9127. --- Resolution: Won't Fix Comment from Bowen Li indicated that this log statement is in fact correct. The

[jira] [Created] (FLINK-9127) Filesystem State Backend logged incorrectly

Scott Kidder created FLINK-9127: --- Summary: Filesystem State Backend logged incorrectly Key: FLINK-9127 URL: https://issues.apache.org/jira/browse/FLINK-9127 Project: Flink Issue Type: Bug

[jira] [Assigned] (FLINK-7021) Flink Task Manager hangs on startup if one Zookeeper node is unresolvable

[ https://issues.apache.org/jira/browse/FLINK-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder reassigned FLINK-7021: --- Assignee: Scott Kidder > Flink Task Manager hangs on startup if one Zookeeper node is

[jira] [Commented] (FLINK-7021) Flink Task Manager hangs on startup if one Zookeeper node is unresolvable

[ https://issues.apache.org/jira/browse/FLINK-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16067189#comment-16067189 ] Scott Kidder commented on FLINK-7021: - Logs from Flink Task Manager during startup when an

[jira] [Commented] (FLINK-7021) Flink Task Manager hangs on startup if one Zookeeper node is unresolvable

[ https://issues.apache.org/jira/browse/FLINK-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066590#comment-16066590 ] Scott Kidder commented on FLINK-7021: - Related to this Curator client library bug:

[jira] [Updated] (FLINK-7021) Flink Task Manager hangs on startup if one Zookeeper node is unresolvable

[ https://issues.apache.org/jira/browse/FLINK-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder updated FLINK-7021: Affects Version/s: 1.3.1 > Flink Task Manager hangs on startup if one Zookeeper node is

[jira] [Created] (FLINK-7022) Flink Job Manager Scheduler & Web Frontend out of sync when Zookeeper is unavailable on startup

Scott Kidder created FLINK-7022: --- Summary: Flink Job Manager Scheduler & Web Frontend out of sync when Zookeeper is unavailable on startup Key: FLINK-7022 URL: https://issues.apache.org/jira/browse/FLINK-7022

[jira] [Created] (FLINK-7021) Flink Task Manager hangs on startup if one Zookeeper node is unresolvable

Scott Kidder created FLINK-7021: --- Summary: Flink Task Manager hangs on startup if one Zookeeper node is unresolvable Key: FLINK-7021 URL: https://issues.apache.org/jira/browse/FLINK-7021 Project: Flink

[jira] [Commented] (FLINK-5898) Race-Condition with Amazon Kinesis KPL

[ https://issues.apache.org/jira/browse/FLINK-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017653#comment-16017653 ] Scott Kidder commented on FLINK-5898: - I created a new build of Flink that uses KPL {{0.12.4}} and AWS

[jira] [Commented] (FLINK-5898) Race-Condition with Amazon Kinesis KPL

[ https://issues.apache.org/jira/browse/FLINK-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017473#comment-16017473 ] Scott Kidder commented on FLINK-5898: - Hi Gordon! I think this issue and FLINK-5946 warrant upgrading

[jira] [Closed] (FLINK-5946) Kinesis Producer uses KPL that orphans threads that consume 100% CPU

[ https://issues.apache.org/jira/browse/FLINK-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder closed FLINK-5946. --- Resolution: Workaround The fix for this issue is included in release `0.12.4` of the AWS KPL,

[jira] [Closed] (FLINK-5898) Race-Condition with Amazon Kinesis KPL

[ https://issues.apache.org/jira/browse/FLINK-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder closed FLINK-5898. --- Resolution: Workaround Issue fixed in KPL version 0.12.4. > Race-Condition with Amazon Kinesis KPL >

[jira] [Commented] (FLINK-5898) Race-Condition with Amazon Kinesis KPL

[ https://issues.apache.org/jira/browse/FLINK-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017444#comment-16017444 ] Scott Kidder commented on FLINK-5898: - The fix for this issue is included in release `0.12.4` of the

[jira] [Commented] (FLINK-5946) Kinesis Producer uses KPL that orphans threads that consume 100% CPU

[ https://issues.apache.org/jira/browse/FLINK-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011273#comment-16011273 ] Scott Kidder commented on FLINK-5946: - FYI: the pull-request against the Kinesis Producer Library

[jira] [Commented] (FLINK-5898) Race-Condition with Amazon Kinesis KPL

[ https://issues.apache.org/jira/browse/FLINK-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011272#comment-16011272 ] Scott Kidder commented on FLINK-5898: - FYI: the pull-request against the Kinesis Producer Library

[jira] [Commented] (FLINK-6176) Add JARs to CLASSPATH deterministically

[ https://issues.apache.org/jira/browse/FLINK-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938990#comment-15938990 ] Scott Kidder commented on FLINK-6176: - The ordering of {{FLINK_CLASSPATH}} entries affected

[jira] [Updated] (FLINK-6176) Add JARs to CLASSPATH deterministically

[ https://issues.apache.org/jira/browse/FLINK-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder updated FLINK-6176: Description: The {{config.sh}} script uses the following shell-script function to build the

[jira] [Created] (FLINK-6176) Add JARs to CLASSPATH deterministically

Scott Kidder created FLINK-6176: --- Summary: Add JARs to CLASSPATH deterministically Key: FLINK-6176 URL: https://issues.apache.org/jira/browse/FLINK-6176 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-5946) Kinesis Producer uses KPL that orphans threads that consume 100% CPU

Scott Kidder created FLINK-5946: --- Summary: Kinesis Producer uses KPL that orphans threads that consume 100% CPU Key: FLINK-5946 URL: https://issues.apache.org/jira/browse/FLINK-5946 Project: Flink

[jira] [Commented] (FLINK-5898) Race-Condition with Amazon Kinesis KPL

[ https://issues.apache.org/jira/browse/FLINK-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883238#comment-15883238 ] Scott Kidder commented on FLINK-5898: - Thanks Gordon & Rob, I've opened a pull-request against the

[jira] [Commented] (FLINK-5898) Race-Condition with Amazon Kinesis KPL

[ https://issues.apache.org/jira/browse/FLINK-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881967#comment-15881967 ] Scott Kidder commented on FLINK-5898: - Hi [~tzulitai], I'll look into fixing this in the KPL. I

[jira] [Created] (FLINK-5898) Race-Condition with Amazon Kinesis KPL

Scott Kidder created FLINK-5898: --- Summary: Race-Condition with Amazon Kinesis KPL Key: FLINK-5898 URL: https://issues.apache.org/jira/browse/FLINK-5898 Project: Flink Issue Type: Bug

[jira] [Closed] (FLINK-5648) Task Manager ID missing from logs link in Job Manager UI

[ https://issues.apache.org/jira/browse/FLINK-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder closed FLINK-5648. --- Resolution: Not A Problem Thank you for trying to reproduce this issue, Robert. I found the sequence

[jira] [Closed] (FLINK-5649) KryoException when starting job from Flink 1.2.0 rc0 savepoint

[ https://issues.apache.org/jira/browse/FLINK-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder closed FLINK-5649. --- Resolution: Fixed Yes, we can close the issue since there's no expectation of compatibility across

[jira] [Updated] (FLINK-5649) KryoException when starting job from Flink 1.2.0 rc0 savepoint

[ https://issues.apache.org/jira/browse/FLINK-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder updated FLINK-5649: Description: I tried to submit a job using a savepoint taken with Flink 1.2.0 rc0 and encountered

[jira] [Created] (FLINK-5649) KryoException when starting job from Flink 1.2.0 rc0 savepoint

Scott Kidder created FLINK-5649: --- Summary: KryoException when starting job from Flink 1.2.0 rc0 savepoint Key: FLINK-5649 URL: https://issues.apache.org/jira/browse/FLINK-5649 Project: Flink

[jira] [Commented] (FLINK-5648) Task Manager ID missing from logs link in Job Manager UI

[ https://issues.apache.org/jira/browse/FLINK-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838860#comment-15838860 ] Scott Kidder commented on FLINK-5648: - May have been introduced in FLINK-5382 pull-request

[jira] [Updated] (FLINK-5648) Task Manager ID missing from logs link in Job Manager UI

[ https://issues.apache.org/jira/browse/FLINK-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder updated FLINK-5648: Description: This appears to be a regression introduced in Flink 1.2.0 rc2. I've been using 1.2.0

[jira] [Created] (FLINK-5648) Task Manager ID missing from logs link in Job Manager UI

Scott Kidder created FLINK-5648: --- Summary: Task Manager ID missing from logs link in Job Manager UI Key: FLINK-5648 URL: https://issues.apache.org/jira/browse/FLINK-5648 Project: Flink Issue

[jira] [Commented] (FLINK-4651) Re-register processing time timers at the WindowOperator upon recovery.

[ https://issues.apache.org/jira/browse/FLINK-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812288#comment-15812288 ] Scott Kidder commented on FLINK-4651: - I can confirm that this issue appears to be fixed in the

[jira] [Updated] (FLINK-5355) Handle AmazonKinesisException gracefully in Kinesis Streaming Connector

[ https://issues.apache.org/jira/browse/FLINK-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder updated FLINK-5355: Affects Version/s: (was: 2.0.0) 1.2.0 > Handle AmazonKinesisException

[jira] [Updated] (FLINK-5355) Handle AmazonKinesisException gracefully in Kinesis Streaming Connector

[ https://issues.apache.org/jira/browse/FLINK-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder updated FLINK-5355: Description: My Flink job that consumes from a Kinesis stream must be restarted at least once

[jira] [Updated] (FLINK-5355) Handle AmazonKinesisException gracefully in Kinesis Streaming Connector

[ https://issues.apache.org/jira/browse/FLINK-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder updated FLINK-5355: Affects Version/s: 2.0.0 > Handle AmazonKinesisException gracefully in Kinesis Streaming Connector

[jira] [Created] (FLINK-5355) Handle AmazonKinesisException gracefully in Kinesis Streaming Connector

Scott Kidder created FLINK-5355: --- Summary: Handle AmazonKinesisException gracefully in Kinesis Streaming Connector Key: FLINK-5355 URL: https://issues.apache.org/jira/browse/FLINK-5355 Project: Flink

[jira] [Created] (FLINK-4622) CLI help message should include 'savepoint' action

Scott Kidder created FLINK-4622: --- Summary: CLI help message should include 'savepoint' action Key: FLINK-4622 URL: https://issues.apache.org/jira/browse/FLINK-4622 Project: Flink Issue Type:

[jira] [Commented] (FLINK-3442) Expose savepoint button on web ui

[ https://issues.apache.org/jira/browse/FLINK-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493485#comment-15493485 ] Scott Kidder commented on FLINK-3442: - This is duplicated by FLINK-4336 > Expose savepoint button on

[jira] [Closed] (FLINK-4536) Possible thread leak in Task Manager

[ https://issues.apache.org/jira/browse/FLINK-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder closed FLINK-4536. --- Resolution: Not A Bug > Possible thread leak in Task Manager > >

[jira] [Commented] (FLINK-4536) Possible thread leak in Task Manager

[ https://issues.apache.org/jira/browse/FLINK-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456481#comment-15456481 ] Scott Kidder commented on FLINK-4536: - On second thought, I'll leave the issue open and allow the

[jira] [Comment Edited] (FLINK-4536) Possible thread leak in Task Manager

[ https://issues.apache.org/jira/browse/FLINK-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456462#comment-15456462 ] Scott Kidder edited comment on FLINK-4536 at 9/1/16 8:04 PM: - Thank you so

[jira] [Commented] (FLINK-4536) Possible thread leak in Task Manager

[ https://issues.apache.org/jira/browse/FLINK-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456462#comment-15456462 ] Scott Kidder commented on FLINK-4536: - Thank you so much [~tzulitai] and [~StephanEwen] for looking

[jira] [Commented] (FLINK-4536) Possible thread leak in Task Manager

[ https://issues.apache.org/jira/browse/FLINK-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15453388#comment-15453388 ] Scott Kidder commented on FLINK-4536: - Here's a chart of the thread count for each Task Manager during

[jira] [Created] (FLINK-4536) Possible thread leak in Task Manager

Scott Kidder created FLINK-4536: --- Summary: Possible thread leak in Task Manager Key: FLINK-4536 URL: https://issues.apache.org/jira/browse/FLINK-4536 Project: Flink Issue Type: Bug

[jira] [Commented] (FLINK-4341) Kinesis connector does not emit maximum watermark properly

[ https://issues.apache.org/jira/browse/FLINK-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428584#comment-15428584 ] Scott Kidder commented on FLINK-4341: - FYI, I've confirmed that explicitly setting the parallelism on

[jira] [Updated] (FLINK-4341) Checkpoint state size grows unbounded when task parallelism not uniform

[ https://issues.apache.org/jira/browse/FLINK-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kidder updated FLINK-4341: Affects Version/s: 1.1.1 > Checkpoint state size grows unbounded when task parallelism not uniform

[jira] [Commented] (FLINK-4341) Checkpoint state size grows unbounded when task parallelism not uniform

[ https://issues.apache.org/jira/browse/FLINK-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425408#comment-15425408 ] Scott Kidder commented on FLINK-4341: - I repeated my tests using Flink 1.1.1 and continue to have

[jira] [Commented] (FLINK-4341) Checkpoint state size grows unbounded when task parallelism not uniform

[ https://issues.apache.org/jira/browse/FLINK-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414599#comment-15414599 ] Scott Kidder commented on FLINK-4341: - Unfortunately I don't have the time to develop a test

[jira] [Commented] (FLINK-4341) Checkpoint state size grows unbounded when task parallelism not uniform

[ https://issues.apache.org/jira/browse/FLINK-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414301#comment-15414301 ] Scott Kidder commented on FLINK-4341: - I also noticed that when checkpointing is enabled and I'm using

[jira] [Created] (FLINK-4341) Checkpoint state size grows unbounded when task parallelism not uniform

Scott Kidder created FLINK-4341: --- Summary: Checkpoint state size grows unbounded when task parallelism not uniform Key: FLINK-4341 URL: https://issues.apache.org/jira/browse/FLINK-4341 Project: Flink

[jira] [Created] (FLINK-4197) Allow Kinesis Endpoint to be Overridden via Config

Scott Kidder created FLINK-4197: --- Summary: Allow Kinesis Endpoint to be Overridden via Config Key: FLINK-4197 URL: https://issues.apache.org/jira/browse/FLINK-4197 Project: Flink Issue Type: