[jira] [Commented] (FLINK-33096) Flink on k8s，if one taskmanager pod was crashed，the whole flink job will be failed

[ https://issues.apache.org/jira/browse/FLINK-33096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767595#comment-17767595 ] wawa commented on FLINK-33096: -- So sorry，correct the previous description:   there was an exception during

[jira] [Commented] (FLINK-33096) Flink on k8s，if one taskmanager pod was crashed，the whole flink job will be failed

[ https://issues.apache.org/jira/browse/FLINK-33096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766652#comment-17766652 ] wawa commented on FLINK-33096: -- [~huweihua] Restart-strategy has been set. Here are the details:

[jira] [Created] (FLINK-33096) Flink on k8s，if one taskmanager pod was crashed，the whole flink job will be failed

wawa created FLINK-33096: Summary: Flink on k8s，if one taskmanager pod was crashed，the whole flink job will be failed Key: FLINK-33096 URL: https://issues.apache.org/jira/browse/FLINK-33096 Project: Flink

[jira] [Created] (FLINK-27653) Pulsar Connector bug: The startCursor has been setted default value of "MessageId.earliest", Every time to restart the job，the Consumer will do the seek operation.

wawa created FLINK-27653: Summary: Pulsar Connector bug: The startCursor has been setted default value of "MessageId.earliest", Every time to restart the job，the Consumer will do the seek operation. Key: FLINK-27653