Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A6B1318DC0 for ; Wed, 2 Mar 2016 21:26:18 +0000 (UTC) Received: (qmail 20819 invoked by uid 500); 2 Mar 2016 21:26:18 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 20784 invoked by uid 500); 2 Mar 2016 21:26:18 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 20752 invoked by uid 99); 2 Mar 2016 21:26:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2016 21:26:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 2A7E22C1F5C for ; Wed, 2 Mar 2016 21:26:18 +0000 (UTC) Date: Wed, 2 Mar 2016 21:26:18 +0000 (UTC) From: "Paulo Motta (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-11258) Repair scheduling - Resource locking API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-11258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176516#comment-15176516 ] 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: https://issues.apache.org/jira/browse/CASSANDRA-11258 > 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 (v6.3.4#6332)