Last active
June 19, 2017 01:09
-
-
Save racheliurui/3f3926ed5fc4b78284919d0093418a27 to your computer and use it in GitHub Desktop.
Kafka Cluster
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Conclusion, | |
| Zookeeper need at least 2 instances to function as cluster coordinator. | |
| When start a new publisher, we need to specify the publish-brokers, | |
| • if all publish-brokers are down but there’s other broker(s) in same replica is up and zookeeper is in function, then the published message will be cached somewhere and re-published when one of the publish-brokers is up | |
| • if all publish-brokers are down and zookeeper is not in function, then we can’t publish | |
| For an existing function publisher, when we bring down some of publish-brokers, | |
| • If all publish-brokers are down and we need to switch to other alive brokers , we need to count on zookeeper | |
| Similar for Consumers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Q: Find out Kafka version.
check the jar under kafka/lib library. (Hortonworks HDF 2.4.2 with kafka v0.10.1 )