-
Notifications
You must be signed in to change notification settings - Fork 269
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
Number of alive brokers '1' does not meet the required replication factor '3' for the transactions state topic #1147
Comments
@alesj Thoughts on this? |
Who / what creates topics required for the Streams topology? |
If it's a single (or < 3) node cluster you should configure transaction.state.log.replication.factor on the broker. |
I tried that, it didn't work so I commented it out:
|
The log message |
It is set. See my broker config at the bottom. I'm getting a different error now: The schema registry logs:
I start up my broker, and create the topics using the below commands. The broker starts up and runs fine. Once I spin up the streams registry, this happens in the logs. I think the issue has something to do with the __transaction_state-XX topic that are auto created. The logs show it being created with [2021-01-20 20:28:28,722] INFO Created log for partition __transaction_state-25 in /var/lib/kafka/data/__transaction_state-25 with properties {compression.type -> uncompressed, message.downconversion.enable -> true, min.insync.replicas -> 2, (as shown below) My topic creation script:
The broker logs:
The below error happens over and over again in the broker logs and the registry web console won't load - saying kstreams isn't running.
|
I solved this by adding these to my broker. Sorry for opening this issue.
|
Glad you figured this out! I'm very happy this issue exists so that hopefully someone in the future will run into this issue and the info you've provided here will help. |
FWIW, this came up for me too. Thanks for the guidance @ebbnflow One thing to add for anyone coming to this late and skipping to the end is that |
@smccarthy-ie something to add to our documentation? |
Hi all,
I am using docker to spin up a kafka broker and zookeeper in a single node config for local development.
When I spin up the kstreams flavor of the registry it brings down my broker.
The Broker logs when spinning up the registry:
The last message is repeated over and over again on a tight loop. Broker becomes non-responsive.
This is the message I get in the web console:
The text was updated successfully, but these errors were encountered: