redpanda-data / redpanda-data/redpanda-operator
Topic replication won't match number of brokers
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 84
- Forks
- 32
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 104
Description
There are two errors This server does not host this topic-partition and Replication factor is below 1 or larger than the number of available brokers despite there being two brokers running.
Spec:
Interval: 3s
Kafka API Spec:
Brokers:
redpanda-alpha-0.redpanda-alpha.operations.svc.cluster.local:9093
redpanda-alpha-1.redpanda-alpha.operations.svc.cluster.local:9093
Partitions: 20
Replication Factor: 2
Status:
Conditions:
Last Transition Time: 2024-08-15T23:48:44Z
Message: Topic reconciliation failed
Observed Generation: 1
Reason: Failed
Status: False
Type: Ready
Observed Generation: 1
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning topicCreationFailure 85s (x12 over 95s) TopicReconciler creating topic ([INVALID_REPLICATION_FACTOR: Replication factor is below 1 or larger than the number of available brokers.]) CreateTopicsResponse error (%!!(MISSING)s(MISSING)): %!!(MISSING)s(MISSING)
Warning topicConfigurationDescribeFailure 74s (x13 over 95s) TopicReconciler describing topic configuration ([UNKNOWN_TOPIC_OR_PARTITION: This server does not host this topic-partition.]) DescribeConfigsResponse error (%!!(MISSING)s(MISSING)): %!!(MISSING)s(MISSING)
JIRA Link: K8S-322
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported topic specification and the two broker endpoints, then consult JIRA K8S-322 for the issue's investigation context. Reproduce topic reconciliation with two brokers and verify that creation and configuration description complete without replication-factor or unknown-topic errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100