[jira] [Commented] (KAFKA-12421) Improve controller's atomic grouping

["Colin McCabe (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487233#comment-17487233 ] 

Colin McCabe commented on KAFKA-12421:
--------------------------------------

We did introduce a distinction between atomic and non-atomic writes, so let's close this for now.

> Improve controller's atomic grouping
> ------------------------------------
>
>                 Key: KAFKA-12421
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12421
>             Project: Kafka
>          Issue Type: Improvement
>          Components: controller
>            Reporter: José Armando García Sancio
>            Assignee: HaiyuanZhao
>            Priority: Major
>              Labels: kip-500
>
> The current controller implementation atomically appends to the metadata log by making sure that all required records are on the same batch. The controller groups all of the records that result from an RPC into one batch. Some of the RPCs are:
>  # Client quota changes
>  # Configuration changes
>  # Feature changes
>  # Topic creation
> This is good enough for correctness but it is more aggressive than necessary. For example, for topic creation since errors are reported independently, the controller only needs to guarantee that all of the records for one topic are committed atomically.



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