Topic Operator's internal Topic created with replication.factor of 1 and min ISR of 2

Solution Unverified - Updated -

Issue

  • We have a 3 node Kafka cluster on OpenShift 4.6 running that was recently updated from AMQ Streams 1.6.0 to 1.7.0.
__strimzi-topic-operator-kstreams-topic-store-changelog is created with replication.factor of 1 and min.insync.replicas of 2.

Topic: __strimzi-topic-operator-kstreams-topic-store-changelog  PartitionCount: 1       ReplicationFactor: 1    Configs: min.insync.replicas=2,cleanup.policy=compact,segment.bytes=67108864,message.format.version=2.1-IV2,min.compaction.lag.ms=0,message.timestamp.type=CreateTime,retention.bytes=209715200
        Topic: __strimzi-topic-operator-kstreams-topic-store-changelog  Partition: 0    Leader: 2       Replicas: 2     Isr: 2
  • Kafka Config default.replication.factor is 3 and min.insync.replicas is 2.

  • Do I need to manually update this topic operator internal topic to have additional replicas? I expected this to honor the broker's default replication factor.

Environment

  • Red Hat AMQ Streams
    • 1.7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content