[ 
https://issues.apache.org/jira/browse/FLINK-17355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-17355:
-----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: 
auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Exactly once kafka checkpointing sensitive to single node failures
> ------------------------------------------------------------------
>
>                 Key: FLINK-17355
>                 URL: https://issues.apache.org/jira/browse/FLINK-17355
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka
>    Affects Versions: 1.10.0
>            Reporter: Teng Fei Liao
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> With exactly one semantics, when checkpointing, FlinkKafkaProducer creates a 
> new KafkaProducer for each checkpoint. KafkaProducer#initTransactions can 
> timeout if a kafka node becomes unavailable, even in the case of multiple 
> brokers and in-sync replicas (see 
> [https://stackoverflow.com/questions/55955379/enabling-exactly-once-causes-streams-shutdown-due-to-timeout-while-initializing]).
> In non-flink cases, this might be fine since I imagine a KafkaProducer is not 
> created very often. With flink however, this is called per checkpoint which 
> means practically an HA kafka cluster isn't actually HA. This makes rolling a 
> kafka node particularly painful even in intentional cases such as config 
> changes or upgrades.
>  
> In our specific setup, these are our settings:
> 5 kafka nodes
> Per topic, we have a replication factor = 3 and in-sync replicas = 2 and 
> partitions = 3



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to