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 Wed, 02 Mar 2016 21:26:18 GMT


Paulo Motta commented on CASSANDRA-11258:

While 4 feels like a workaround, and 3 would probably make LWT more complex, I think 2 is
probably the best option here, and this wouldn't prevent 1 from being pursued in the future.

While I think we could add a new VERB ({{REMOTE_CAS}}) to the messaging service without a
protocol bump (by reusing the {{UNUSED_X}} verbs), I think we could this in a separate ticket
to avoid losing focus here.

So I propose we use a global CAS ({{SERIAL}} consistency) for each DC lock for the first version,
which should make multi-dc schedule repairs work when there is no network partition, and improve
later when the {{REMOTE_CAS}} verb is in place. WDYT?

> 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