When using ZK to keep track of last offsets metrics etc., how do you know
when you are pushing your ZK cluster to its limit?
Or can ZK handle thousands of writes/reads per second no problem since it
is all in-memory? But even so, you need some idea on its upper limits and
how close you are to tha
You might look at Curator http://curator.apache.org/
On Mon, Dec 9, 2013 at 12:36 PM, S Ahmed wrote:
> Say am I doing this, a scenerio that I just came up with that demonstrates
> #2.
>
> Someone signs up on a website, and you have to:
>
> 1. create the user profile
> 2. send email confirmation
Say am I doing this, a scenerio that I just came up with that demonstrates
#2.
Someone signs up on a website, and you have to:
1. create the user profile
2. send email confirmation email
3. resize avatar
Now once a person registers on a website, I write a message to Kafka.
Now I have 3 differe
We use Zookeeper, as is standard with Kafka.
Our systems are idempotent, so we only store offsets when the message is
fully processed. If this means we occasionally replay a message due to some
corner-case, or simply a restart, it doesn't matter.
Philip
On Mon, Dec 9, 2013 at 12:28 PM, S Ahmed
I was hoping people could comment on how they handle the following
scenerios:
1. Storing the last successfully processed messageId/Offset. Are people
using mysql, redis, etc.? What are the tradeoffs here?
2. How do you handle recovering from an error while processesing a given
event?
There are
