Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (nike.apache.org: domain of tivv00@gmail.com designates
 209.85.213.176 as permitted sender)
MIME-Version: 1.0
From: Vitalii Tymchyshyn <vit@tym.im>
Date: Wed, 04 Feb 2015 20:10:49 +0000
Message-ID: 
 <CABWW-d1XbfcWACiSLeW9+-AbLOAGJ5xwcsN13dyMWi-uy=2aQQ@mail.gmail.com>
Subject: Implementing sharding with zookeeper
To: user@zookeeper.apache.org
Content-Type: multipart/alternative; boundary=089e0122acca9f37ba050e48c83b

--089e0122acca9f37ba050e48c83b
Content-Type: text/plain; charset=UTF-8

Hello.

I have a task that looks like a fit for Zookeeper and I thought I find a
recipe in Curator, but I dont. So, It looks like I need my own recipe.

The problem is: we have a stream of tasks coming in. All tasks for the same
account must be done sequential. But for different accounts it's OK to do
in parallel, so we want workers to distribute account space between them.

The first step, of course, is to make an account hash to ensure load is
distributed as smooth as possible.

Next I could simply use a lot of locks, but this way I can't ensure
fairness.

Thats why I think I need a Leader who will distribute (or redistribute in
case of node death) the hash space between the live nodes.

What do you think? May be I am missing something and there is existing
recipe for the task?

Best regards, Vitalii Tymchyshyn

--089e0122acca9f37ba050e48c83b--