[
https://issues.apache.org/jira/browse/KAFKA-15430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Vysotskiy updated KAFKA-15430:
-------------------------------------
Priority: Major (was: Minor)
> Kafla create replca partition on controller node
> ------------------------------------------------
>
> Key: KAFKA-15430
> URL: https://issues.apache.org/jira/browse/KAFKA-15430
> Project: Kafka
> Issue Type: Test
> Components: kraft
> Affects Versions: 3.5.1
> Reporter: Andrii Vysotskiy
> Priority: Major
>
> I have configuration 5 nodes (KRAFT mode), with next roles: 4
> broker+controller and 1 controller. Create topic with replication factor 5,
> and it is created, and describe show that topic partition have 5 replicas.
>
> {{/opt/kafka/latest/bin/kafka-topics.sh --create
> --bootstrap-server=dc1-prod-kafka-001-vs:9092 --replication-factor 5
> --partitions 1 --topic test5}}
>
> /opt/kafka/latest/bin/kafka-topics.sh --describe --topic test5
> --bootstrap-server=dc1-prod-kafka-001-vs:9092
> Topic: test5 TopicId: amuqr8EgRmqeKryUHZwsMA PartitionCount: 1
> ReplicationFactor: 5 Configs: segment.bytes=1073741824
> Topic: test5 Partition: 0 Leader: 3 Replicas: 3,4,1,2,5 Isr: 3,4,1,2}}
>
> Replicas 5 and ISR 4. Why does kafka initially allow you to create a replica
> on the controller node, although in reality the replica is not created on the
> controller node and there are no topic files in the log directory.
> Is this expected behavior or not? Thanks.
> I want to understand whether such behavior is the norm for Kafka
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
