Member since
11-21-2018
4
Posts
0
Kudos Received
0
Solutions
11-21-2018
08:31 AM
Thanks a lot for your help and your time @Tomas79, I will try this solution.
... View more
11-21-2018
07:41 AM
@Tomas79 wrote: Yes, it could be the case. Thanks @Tomas79, I need to make sure because all teams in my compagny are pressuring me about this answer 🙂 They need me to make sure the topics are with the min.insync.replicas=2 If you have a way to check that, it would be perfect.
... View more
11-21-2018
07:31 AM
Thanks @Tomas79, When launching the command again (after having changed the default value from 1 to 2) and create a new topic "TOPICtest2" afterward, I still don't see the property in the result of the command: kafka-topics --zookeeper ServerName:2181 --topic TOPICtest2 --describe . . Result: Topic:TOPICTEST PartitionCount:3 ReplicationFactor:3 Configs:retention.ms=172800000 Does this mean that the value (min.insync.replicas=2) is not showed when the topic has the default value?
... View more
11-21-2018
05:32 AM
Hi, I need to know if the "min.insync.replicas" configured with a new value (2) is taking effect on all of our Topics that was already created before the change of this value. What I've already done: - I noticed that when I execute the command: kafka-topics --zookeeper ServerName:2181 --topic TOPICTEST --describe I have this result: Topic:TOPICTEST PartitionCount:3 ReplicationFactor:3 Configs:retention.ms=172800000 ==> I don't see the "min.insync.replicas=2" result I see it only when I alter the topic this way: kafka-topics --alter --zookeeper ServerName:2181 --topic TOPICTEST --config min.insync.replicas=2 Then the result is of the same --describe is: Topic:TOPICTEST PartitionCount:3 ReplicationFactor:3 Configs:retention.ms=172800000,min.insync.replicas=2 Which confirms that the min.insync.replicas value has been taken into account. How can I check the new default value is applied as planned? Thanks, Jo
... View more
Labels:
- Labels:
-
Apache Kafka
-
Apache Zookeeper