cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11258) Repair scheduling - Resource locking API
Date Sat, 05 Mar 2016 03:59:40 GMT


Paulo Motta commented on CASSANDRA-11258:

bq. However, if we want to visualize all data center locks to the user, it would be more complex
to do so.

That's a good point, we might want to view remote locks in the future so I'm not sure {{LDCRS}}
would be a good fit in this case. We could maybe save the remote lock info in the local keyspace
but this wouldn't be very different (and probably more complex) than having a global keyspace.
And we might also want to introduce global locks in the future, so we would need a global
keyspace in addition to the local one.

bq. Should we start with SimpleStrategy and a replication of 3 then?

Yes, I think we should advance the implementation based on {{SimpleStrategy}} for now and
focus on single DC first, and think better about multi-DC support in a separate task (since
it may become easier to reason about multi-DC details when we have a full scheduled repair
cycle working for a single DC).

> Repair scheduling - Resource locking API
> ----------------------------------------
>                 Key: CASSANDRA-11258
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Marcus Olsson
>            Assignee: Marcus Olsson
>            Priority: Minor
> Create a resource locking API & implementation that is able to lock a resource in
a specified data center. It should handle priorities to avoid node starvation.

This message was sent by Atlassian JIRA

View raw message