-
Notifications
You must be signed in to change notification settings - Fork 682
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Compose - ERROR Broker #139
Comments
I have The same error when Trying to start a single Broker on Kraft mode. [2024-02-14 11:49:15,004] INFO [Controller 1] CreateTopics result(s): CreatableTopic(name='_confluent-link-metadata', numPartitions=50, replicationFactor=3, assignments=[], configs=[CreateableTopicConfig(name='cleanup.policy', value='compact'), CreateableTopicConfig(name='min.insync.replicas', value='2')], linkName=null, mirrorTopic=null, sourceTopicId=AAAAAAAAAAAAAAAAAAAAAA, mirrorStartOffsetSpec=-9223372036854775808, mirrorStartOffsets=[]): INVALID_REPLICATION_FACTOR (Unable to replicate the partition 3 time(s): The target replication factor of 3 cannot be reached because only 1 broker(s) are registered.) (org.apache.kafka.controller.ReplicationControlManager) |
Finaly i modify my docker-compose file to override all default replications to 1 and it solve it : |
I have just tried this, and it is not working for me. |
I can confirm this seemed to work for me. Thanks. |
I can confirm none of these options worked for me. |
What does your docker compose look like? |
The actual goal is/was to have a lean docker compose file starting up the components I care about (broker, rest proxy, schema registry) given the localhost-first schema registry tutorial I'm busy with. The source is here which is ultimately straight from Confluent (of course docker compose files like this do not inspire confidence). As an aside, in my case I only noticed the various replication factor complaints as I started docker-compose without the daemon mode flag. The one entry that is working reliably is this one, hence still there:
|
I stumbled into the same issue, and this line needs to be added to the set of environment:
# ...
KAFKA_METRIC_REPORTERS: io.confluent.metrics.reporter.ConfluentMetricsReporter
KAFKA_CONFLUENT_METRICS_REPORTER_BOOTSTRAP_SERVERS: broker:9092
KAFKA_CONFLUENT_METRICS_REPORTER_TOPIC_REPLICAS: 1 <------ this one
# ... |
Description
After docker compose up
ERROR broker=1 is storing logs in /tmp/kraft-combined-logs, Kafka expects to store log data in a persistent location (io.confluent.controlcenter.healthcheck.AllHealthCheck)
broker | [2024-01-09 09:28:19,376] INFO [Controller 1] CreateTopics result(s): CreatableTopic(name='_confluent-link-metadata', numPartitions=50, replicationFactor=3, assignments=[], configs=[CreateableTopicConfig(name='cleanup.policy', value='compact'), CreateableTopicConfig(name='min.insync.replicas', value='2')], linkName=null, mirrorTopic=null, sourceTopicId=AAAAAAAAAAAAAAAAAAAAAA, mirrorStartOffsetSpec=-9223372036854775808, mirrorStartOffsets=[]): INVALID_REPLICATION_FACTOR (Unable to replicate the partition 3 time(s): The target replication factor of 3 cannot be reached because only 1 broker(s) are registered.) (org.apache.kafka.controller.ReplicationControlManager)
The text was updated successfully, but these errors were encountered: