[
https://issues.apache.org/jira/browse/KAFKA-19622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101091#comment-18101091
]
Yunseop Eom commented on KAFKA-19622:
-------------------------------------
Update on PR #22938: https://github.com/apache/kafka/pull/22938
The documentation now distinguishes the short hybrid-mode restart window from
the longer dual-write validation phase, explains operational checks, and makes
migration finalization irreversibility explicit.
Validation completed with :core:siteDocsTar and git diff --check; the generated
site-docs archive was inspected. GitHub CI is green and the PR is open awaiting
review.
> Limitations of KRAFT Dual Write Mode for Production Support
> -----------------------------------------------------------
>
> Key: KAFKA-19622
> URL: https://issues.apache.org/jira/browse/KAFKA-19622
> Project: Kafka
> Issue Type: Task
> Components: documentation, kraft, migration
> Affects Versions: 3.9.0
> Reporter: Sharad Garg
> Priority: Minor
>
> We are currently running Kafka version 3.9.0 and are in the process of
> migrating to KRaft. As part of the migration, we intend to operate in
> dual-write mode in production for an initial period to help identify and
> address any issues.
> Are there any known limitations or risks associated with running in
> dual-write mode? Would you recommend maintaining this mode for production
> stability, and are there best practices we should follow?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
