4 ms·
I submitted a question in previous discussion link[0] but I didn't get an answer by author. But hopefully someone will answer here: How did you solve producer
by majidazimi 8y ago
I submitted a question in previous discussion link[0] but I didn't get an answer by author. But hopefully someone will answer here:
How did you solve producer fencing mechanism which was built into Bookkeeper with Kafka (Assume I need to limit only one client to be able to write to a topic)?
[0] https://news.ycombinator.com/item?id=18559284 https://news.ycombinator.com/item?id=18559284
- Pixelstime 8y agoSorry for that I didn't understand your question fully, I suggest you to ask question in the slack[link] of BookKeeper community. [link]http://bookkeeper.apache.org/community/slack/ http://bookkeeper.apache.org/community/slack/
- majidazimi 8y agoSorry for my bad English. Here is a better explanation: In Bookkeeper, one producer can fence the current active producer from appending to log. If majority of Bookkeeper nodes respond with OK to a FENCE request, then the current producer can not append to the log. This helps implementing master-slave database replication quiet trivial. Master keeps appending to log, and slaves keep reading from log. In case master fails, one of the slaves sends a FENCE request to Bookkeeper nodes which reliably blocks current Mal-functioning master from appending to db log. However in Kafka, this isn't a native operation. Any client can push to a topic. There is no easy way to safely do this. I was looking forward to see how Twitter team actually handled this specific use case.