You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Roman Khachatryan (Jira)" <ji...@apache.org> on 2026/06/04 17:04:00 UTC
[jira] [Assigned] (FLINK-39854) Log JobID in KafkaCommitter
[ https://issues.apache.org/jira/browse/FLINK-39854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Khachatryan reassigned FLINK-39854:
-----------------------------------------
Assignee: Aleksandr Savonin
> Log JobID in KafkaCommitter
> ---------------------------
>
> Key: FLINK-39854
> URL: https://issues.apache.org/jira/browse/FLINK-39854
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Kafka
> Reporter: Aleksandr Savonin
> Assignee: Aleksandr Savonin
> Priority: Minor
>
> We have multiple logs in {{KafkaCommitter}} that will benefit from having {{JobId}} in the logs.
> E.g.
> {code:java}
> LOG.warn(
> "Unable to commit transaction ({}) because its producer is already fenced."
> + " If this warning appears as part of the recovery of a checkpoint, it is expected in some cases (e.g., aborted checkpoints in previous attempt)."
> + " If it's outside of recovery, this means that you either have a different sink with the same '{}'"
> + " or recovery took longer than '{}' ({}ms). In both cases this most likely signals data loss,"
> + " please consult the Flink documentation for more details.",
> request,
> ProducerConfig.TRANSACTIONAL_ID_CONFIG,
> ProducerConfig.TRANSACTION_TIMEOUT_CONFIG,
> kafkaProducerConfig.getProperty(ProducerConfig.TRANSACTION_TIMEOUT_CONFIG),
> e); {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)