Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 15 Apr 2011 07:56:06 +0000 (UTC)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1670124297.60098.1302854166144.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HBASE-3787) Increment is non-idempotent but
 client retries RPC
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Increment is non-idempotent but client retries RPC
--------------------------------------------------

                 Key: HBASE-3787
                 URL: https://issues.apache.org/jira/browse/HBASE-3787
             Project: HBase
          Issue Type: Bug
          Components: client
            Reporter: dhruba borthakur
            Assignee: dhruba borthakur


The HTable.increment() operation is non-idempotent. The client retries the increment RPC a few times (as specified by configuration) before throwing an error to the application. This makes it possible that the same increment call be applied twice at the server.

For increment operations, is it better to use HConnectionManager.getRegionServerWithoutRetries()? Another  option would be to enhance the IPC module to make the RPC server correctly identify if the RPC is a retry attempt and handle accordingly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira