[jira] [Created] (FLINK-33486) Pulsar Client Send Timeout Terminates TaskManager

Jason Kania created FLINK-33486: --- Summary: Pulsar Client Send Timeout Terminates TaskManager Key: FLINK-33486 URL: https://issues.apache.org/jira/browse/FLINK-33486 Project: Flink Issue Type:

[jira] [Updated] (FLINK-33135) Flink Pulsar Connector Attempts Partitioned Routing on Unpartitioned Topic

[ https://issues.apache.org/jira/browse/FLINK-33135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Kania updated FLINK-33135: Description: For a non-partitioned topic, the Flink Pulsar connector creates a TopicRouter,

[jira] [Updated] (FLINK-33135) Flink Pulsar Connector Attempts Partitioned Routing on Unpartitioned Topic

[ https://issues.apache.org/jira/browse/FLINK-33135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Kania updated FLINK-33135: Description: For a non-partitioned topic, the Flink Pulsar connector creates a TopicRouter,

[jira] [Updated] (FLINK-33135) Flink Pulsar Connector Attempts Partitioned Routing on Unpartitioned Topic

[ https://issues.apache.org/jira/browse/FLINK-33135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Kania updated FLINK-33135: Description: For a non-partitioned topic, the Flink Pulsar connector creates a TopicRouter,

[jira] [Updated] (FLINK-33135) Flink Pulsar Connector Attempts Partitioned Routing on Unpartitioned Topic

[ https://issues.apache.org/jira/browse/FLINK-33135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Kania updated FLINK-33135: Description: For a non-partitioned topic, the Flink Pulsar connector creates a TopicRouter,

[jira] [Created] (FLINK-33136) Flink Pulsar Connector RoundRobinTopicRouter Generates Invalid Error Message

Jason Kania created FLINK-33136: --- Summary: Flink Pulsar Connector RoundRobinTopicRouter Generates Invalid Error Message Key: FLINK-33136 URL: https://issues.apache.org/jira/browse/FLINK-33136 Project:

[jira] [Created] (FLINK-33135) Flink Pulsar Connector Attempts Partitioned Routing on Unpartitioned Topic

Jason Kania created FLINK-33135: --- Summary: Flink Pulsar Connector Attempts Partitioned Routing on Unpartitioned Topic Key: FLINK-33135 URL: https://issues.apache.org/jira/browse/FLINK-33135 Project:

[jira] [Updated] (FLINK-33111) Flink Pulsar Connector to Pulsar Client Version Mismatch

[ https://issues.apache.org/jira/browse/FLINK-33111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Kania updated FLINK-33111: Description: In the documentation for the Flink Pulsar Connector,

[jira] [Created] (FLINK-33111) Flink Pulsar Connector to Pulsar Client Version Mismatch

Jason Kania created FLINK-33111: --- Summary: Flink Pulsar Connector to Pulsar Client Version Mismatch Key: FLINK-33111 URL: https://issues.apache.org/jira/browse/FLINK-33111 Project: Flink Issue

[jira] [Commented] (FLINK-24302) Direct buffer memory leak on Pulsar connector with Java 11

[ https://issues.apache.org/jira/browse/FLINK-24302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17632436#comment-17632436 ] Jason Kania commented on FLINK-24302: - [~syhily] The Pulsar team is asking for the entire stack

[jira] [Commented] (FLINK-27611) ConcurrentModificationException during Flink-Pulsar checkpoint notification

[ https://issues.apache.org/jira/browse/FLINK-27611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598045#comment-17598045 ] Jason Kania commented on FLINK-27611: - Understood, unfortunately, it is a blocker for us, just not

[jira] [Commented] (FLINK-27611) ConcurrentModificationException during Flink-Pulsar checkpoint notification

[ https://issues.apache.org/jira/browse/FLINK-27611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17581330#comment-17581330 ] Jason Kania commented on FLINK-27611: - May I ask why this fix was not included in the 1.15.2

[jira] [Commented] (FLINK-27611) ConcurrentModificationException during Flink-Pulsar checkpoint notification

[ https://issues.apache.org/jira/browse/FLINK-27611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558211#comment-17558211 ] Jason Kania commented on FLINK-27611: - Is there a possibility of this getting into the 1.15.1 patch

[jira] [Commented] (FLINK-27611) ConcurrentModificationException during Flink-Pulsar checkpoint notification

[ https://issues.apache.org/jira/browse/FLINK-27611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541478#comment-17541478 ] Jason Kania commented on FLINK-27611: - Does the most recent comment mean that it should go to the

[jira] [Updated] (FLINK-27611) ConcurrentModificationException during Flink-Pulsar checkpoint notification

[ https://issues.apache.org/jira/browse/FLINK-27611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Kania updated FLINK-27611: Component/s: Connectors / Pulsar > ConcurrentModificationException during Flink-Pulsar checkpoint

[jira] [Updated] (FLINK-27611) ConcurrentModificationException during Flink-Pulsar checkpoint notification

[ https://issues.apache.org/jira/browse/FLINK-27611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Kania updated FLINK-27611: Issue Type: Bug (was: Improvement) > ConcurrentModificationException during Flink-Pulsar

[jira] [Created] (FLINK-27611) ConcurrentModificationException during Flink-Pulsar checkpoint notification

Jason Kania created FLINK-27611: --- Summary: ConcurrentModificationException during Flink-Pulsar checkpoint notification Key: FLINK-27611 URL: https://issues.apache.org/jira/browse/FLINK-27611 Project:

[jira] [Created] (FLINK-27568) Cannot submit JobGraph

Jason Kania created FLINK-27568: --- Summary: Cannot submit JobGraph Key: FLINK-27568 URL: https://issues.apache.org/jira/browse/FLINK-27568 Project: Flink Issue Type: Bug Affects Versions:

[jira] [Commented] (FLINK-16468) BlobClient rapid retrieval retries on failure opens too many sockets

[ https://issues.apache.org/jira/browse/FLINK-16468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227405#comment-17227405 ] Jason Kania commented on FLINK-16468: - Up until now, I have been redirected from these activities.

[jira] [Commented] (FLINK-16468) BlobClient rapid retrieval retries on failure opens too many sockets

[ https://issues.apache.org/jira/browse/FLINK-16468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17114190#comment-17114190 ] Jason Kania commented on FLINK-16468: - Sorry [~gjy], not to this point. The current economic/health

[jira] [Commented] (FLINK-16468) BlobClient rapid retrieval retries on failure opens too many sockets

[ https://issues.apache.org/jira/browse/FLINK-16468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066231#comment-17066231 ] Jason Kania commented on FLINK-16468: - [~gjy], the situation is unreliably unreliable, but I will

[jira] [Commented] (FLINK-16468) BlobClient rapid retrieval retries on failure opens too many sockets

[ https://issues.apache.org/jira/browse/FLINK-16468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065174#comment-17065174 ] Jason Kania commented on FLINK-16468: - [~gjy], In looking at my particular situation as a reference,

[jira] [Commented] (FLINK-16468) BlobClient rapid retrieval retries on failure opens too many sockets

[ https://issues.apache.org/jira/browse/FLINK-16468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064899#comment-17064899 ] Jason Kania commented on FLINK-16468: - [~gjy], to me, as a user, your restart strategy seems to lack

[jira] [Commented] (FLINK-16475) PulsarConsumerSource messageReceiveTimeoutMs parameter should be configurable

[ https://issues.apache.org/jira/browse/FLINK-16475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063683#comment-17063683 ] Jason Kania commented on FLINK-16475: - Sorry, was confused because Pulsar switched from tracking in

[jira] [Commented] (FLINK-16468) BlobClient rapid retrieval retries on failure opens too many sockets

[ https://issues.apache.org/jira/browse/FLINK-16468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061785#comment-17061785 ] Jason Kania commented on FLINK-16468: - [~gjy] I will happily update the user docs, but would

[jira] [Commented] (FLINK-16468) BlobClient rapid retrieval retries on failure opens too many sockets

[ https://issues.apache.org/jira/browse/FLINK-16468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17060282#comment-17060282 ] Jason Kania commented on FLINK-16468: - [~gjy] These were reported on the same day but were the

[jira] [Commented] (FLINK-16468) BlobClient rapid retrieval retries on failure opens too many sockets

[ https://issues.apache.org/jira/browse/FLINK-16468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057498#comment-17057498 ] Jason Kania commented on FLINK-16468: - [~NicoK], I will try the blob.fetch.retries settings and see.

[jira] [Commented] (FLINK-16470) Network failure causes Checkpoint Coordinator to flood disk with exceptions

[ https://issues.apache.org/jira/browse/FLINK-16470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056583#comment-17056583 ] Jason Kania commented on FLINK-16470: - [~gjy], the restart strategy was just the default and had no

[jira] [Commented] (FLINK-16468) BlobClient rapid retrieval retries on failure opens too many sockets

[ https://issues.apache.org/jira/browse/FLINK-16468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056533#comment-17056533 ] Jason Kania commented on FLINK-16468: - [~azagrebin], the only thing I saw was a lot of repeats of

[jira] [Created] (FLINK-16475) PulsarConsumerSource messageReceiveTimeoutMs parameter should be configurable

Jason Kania created FLINK-16475: --- Summary: PulsarConsumerSource messageReceiveTimeoutMs parameter should be configurable Key: FLINK-16475 URL: https://issues.apache.org/jira/browse/FLINK-16475 Project:

[jira] [Created] (FLINK-16470) Network failure causes Checkpoint Coordinator to flood disk with exceptions

Jason Kania created FLINK-16470: --- Summary: Network failure causes Checkpoint Coordinator to flood disk with exceptions Key: FLINK-16470 URL: https://issues.apache.org/jira/browse/FLINK-16470 Project:

[jira] [Updated] (FLINK-15744) Some TaskManager Task exceptions are logged as info

[ https://issues.apache.org/jira/browse/FLINK-15744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Kania updated FLINK-15744: Summary: Some TaskManager Task exceptions are logged as info (was: Some TaskManager Task

[jira] [Created] (FLINK-16468) BlobClient rapid retrieval retries on failure opens too many sockets

Jason Kania created FLINK-16468: --- Summary: BlobClient rapid retrieval retries on failure opens too many sockets Key: FLINK-16468 URL: https://issues.apache.org/jira/browse/FLINK-16468 Project: Flink

[jira] [Created] (FLINK-15744) Some TaskManager Task exception are logged as info

Jason Kania created FLINK-15744: --- Summary: Some TaskManager Task exception are logged as info Key: FLINK-15744 URL: https://issues.apache.org/jira/browse/FLINK-15744 Project: Flink Issue Type:

[jira] [Commented] (FLINK-11799) KryoSerializer/OperatorChain ignores copy failure resulting in NullPointerException

[ https://issues.apache.org/jira/browse/FLINK-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814589#comment-16814589 ] Jason Kania commented on FLINK-11799: - Hi Liya,   Your approach seems reasonable. Thanks, Jason

[jira] [Created] (FLINK-11799) KryoSerializer/OperatorChain ignores copy failure resulting in NullPointerException

Jason Kania created FLINK-11799: --- Summary: KryoSerializer/OperatorChain ignores copy failure resulting in NullPointerException Key: FLINK-11799 URL: https://issues.apache.org/jira/browse/FLINK-11799

[jira] [Commented] (FLINK-8035) Unable to submit job when HA is enabled

[ https://issues.apache.org/jira/browse/FLINK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16622792#comment-16622792 ] Jason Kania commented on FLINK-8035: I would need to know the specific logs you would like to see and

[jira] [Commented] (FLINK-8035) Unable to submit job when HA is enabled

[ https://issues.apache.org/jira/browse/FLINK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615275#comment-16615275 ] Jason Kania commented on FLINK-8035: I encountered this issue in 1.5.3 and subsequently had to roll

[jira] [Commented] (FLINK-8035) Unable to submit job when HA is enabled

[ https://issues.apache.org/jira/browse/FLINK-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605052#comment-16605052 ] Jason Kania commented on FLINK-8035: This issue affects more than just submission. Many of the flink

[jira] [Created] (FLINK-9371) High Availability JobManager Registration Failure

Jason Kania created FLINK-9371: -- Summary: High Availability JobManager Registration Failure Key: FLINK-9371 URL: https://issues.apache.org/jira/browse/FLINK-9371 Project: Flink Issue Type: Bug