Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Mon, 6 Apr 2015 21:42:12 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12818717.1428356519000.8032.1428356532841@Atlassian.JIRA>
In-Reply-To: <JIRA.12818717.1428356519000@Atlassian.JIRA>
References: <JIRA.12818717.1428356519000@Atlassian.JIRA>
 <JIRA.12818717.1428356519817@arcas>
Subject: [jira] [Created] (HBASE-13415) Procedure V2 - Use nonces for double
 submits from client
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Enis Soztutar created HBASE-13415:
-------------------------------------

             Summary: Procedure V2 - Use nonces for double submits from client
                 Key: HBASE-13415
                 URL: https://issues.apache.org/jira/browse/HBASE-13415
             Project: HBase
          Issue Type: Sub-task
            Reporter: Enis Soztutar


The client can submit a procedure, but before getting the procId back, the master might fail. In this case, the client request will fail and the client will re-submit the request. If 1.1 client or if there is no contention for the table lock, the time window is pretty small, but still might happen. 

If the proc was accepted and stored in the procedure store, a re-submit from the client will add another procedure, which will execute after the first one. The first one will likely succeed, and the second one will fail (for example in the case of create table, the second one will throw TableExistsException). 

One idea is to use client generated nonces (that we already have) to guard against these cases. The client will submit the request with the nonce and the nonce will be saved together with the procedure in the store. In case of a double submit, the nonce-cache is checked and the procId of the original request is returned. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)