Hi There,

We are toying around with a use case for ZooKeeper to maintain a ban list – either IP based or user ID based that is controlled via ZooKeeper.  In short – if you meet certain suspicious activity your user ID or IP address gets added to a ZooKeeper controlled config file that then propagates out to clients and can drop to associated traffic.

I am curious if anyone has done anything similar with ZooKeeper and has any lessons learned?

Thanks
Ben

Sounds like a reasonable way to go.

Keeping the config as a single (or a few) file is an important thing.
I presume that your update rate will be reasonable.

On Fri, Jun 10, 2011 at 4:12 AM, Ben Hall <[EMAIL PROTECTED]> wrote:
> Hi There,
>
> We are toying around with a use case for ZooKeeper to maintain a ban list – either IP based or user ID based that is controlled via ZooKeeper.  In short – if you meet certain suspicious activity your user ID or IP address gets added to a ZooKeeper controlled config file that then propagates out to clients and can drop to associated traffic.
>
> I am curious if anyone has done anything similar with ZooKeeper and has any lessons learned?
>
> Thanks
> Ben
>

Ha! I was just reading about the Google AI challenge (http://ai-contest.com/),
and when I saw the subject of this post I was very intrigued.

Funny.

Ishaaq

On 10 June 2011 12:12, Ben Hall <[EMAIL PROTECTED]> wrote:

> Hi There,
>
> We are toying around with a use case for ZooKeeper to maintain a ban list –
> either IP based or user ID based that is controlled via ZooKeeper.  In short
> – if you meet certain suspicious activity your user ID or IP address gets
> added to a ZooKeeper controlled config file that then propagates out to
> clients and can drop to associated traffic.
>
> I am curious if anyone has done anything similar with ZooKeeper and has any
> lessons learned?
>
> Thanks
> Ben
>