FWIW I would recommend first trying to solve the issue in your application rather than with Cages or Zoo Keeper. Although I do not have experience with Cages or Zoo Keeper, it's another major server component in your stack.
Hope that helps.
On 08 Nov, 2010,at 02:05 PM, Mubarak Seyed <email@example.com> wrote:
Can someone please validate and recommend a solution for the given design problem?
Problem statement: Need to de-queue data from Cassandra (from Standard ColumnFamily) using a job but multiple instances of a job can run simultaneously (kinda multiple threads), trying to access a same row but need to make sure that only one instance of a job (thread) can access a row, meaning if job A is accessing Row #1, then job B can't access Row #1.
Solution #2: Using some home-grown approach to store/maintain who is accessing what, meaning which job is accessing which row.
Are there any other solutions to the above problem?
Can someone please help me on validate the design?