Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E985F9AFE for ; Thu, 29 Sep 2011 21:10:10 +0000 (UTC) Received: (qmail 465 invoked by uid 500); 29 Sep 2011 21:10:10 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 432 invoked by uid 500); 29 Sep 2011 21:10:10 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 424 invoked by uid 99); 29 Sep 2011 21:10:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Sep 2011 21:10:10 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Sep 2011 21:10:08 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id C86DF2A1217 for ; Thu, 29 Sep 2011 21:09:46 +0000 (UTC) Date: Thu, 29 Sep 2011 21:09:46 +0000 (UTC) From: "jiraposter@reviews.apache.org (Commented) (JIRA)" To: issues@hbase.apache.org Message-ID: <2024396220.9078.1317330586822.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1263753555.454.1317147225709.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-4497) If region opening fails after updating META HBCK reports it as inconsistent and scanning the region throws NSRE MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117617#comment-13117617 ] jiraposter@reviews.apache.org commented on HBASE-4497: ------------------------------------------------------ ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2118/ ----------------------------------------------------------- Review request for hbase. Summary ------- Adds a checkAndPut that takes a timestamp This addresses bug hbase-4497. https://issues.apache.org/jira/browse/hbase-4497 Diffs ----- src/main/java/org/apache/hadoop/hbase/ipc/HRegionInterface.java 3679c02 src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java 7cbdb98 src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java 0c06f4f src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java 99b34cc Diff: https://reviews.apache.org/r/2118/diff Testing ------- Thanks, Michael > If region opening fails after updating META HBCK reports it as inconsistent and scanning the region throws NSRE > --------------------------------------------------------------------------------------------------------------- > > Key: HBASE-4497 > URL: https://issues.apache.org/jira/browse/HBASE-4497 > Project: HBase > Issue Type: Bug > Reporter: ramkrishna.s.vasudevan > Priority: Critical > > As per the discussion in the mail chain "HBCK reporting of possible mismatch in RS assignment" this JIRA is created. > Consider two RS-> RS1 and RS2. > A region tries to open in RS1. But it takes a while. The RS1 has still not updated meta and transitioned the node from OPENING to OPENED > So timeout assigns the region to RS2. RS2 successfully updates the META and opens the region. > Now RS1 tries to act on the region by first updating the META and then transiting the node to OPENING to OPENED. > RS1 transiting the node to OPENING to OPENED will fail. But the META entry will have RS1 as the latest. > Now HBCK reports this as an inconsistency and if we try to scan the Region we get NotServingRegionException. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira