Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 13 Mar 2014 03:04:44 +0000 (UTC)
From: "Anoop Sam John (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12694852.1392242274572.57131.1394679884811@arcas>
In-Reply-To: <JIRA.12694852.1392242274572@arcas>
References: <JIRA.12694852.1392242274572@arcas>
Subject: [jira] [Commented] (HBASE-10514) Forward port HBASE-10466, possible
 data loss when failed flushes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-10514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932832#comment-13932832 ] 

Anoop Sam John commented on HBASE-10514:
----------------------------------------

Oh..  whatever doubt was there in my mind seems not an issue..  Reading these lines
{code}
synchronized (writestate) {
      // Disable compacting and flushing by background threads for this
      // region.
      writestate.writesEnabled = false;
      LOG.debug("Closing " + this + ": disabling compactions & flushes");
      waitForFlushesAndCompactions();
    }
    // If we were not just flushing, is it worth doing a preflush...one
    // that will clear out of the bulk of the memstore before we put up
    // the close flag?
    if (!abort && worthPreFlushing()) {
{code}

> Forward port HBASE-10466, possible data loss when failed flushes
> ----------------------------------------------------------------
>
>                 Key: HBASE-10514
>                 URL: https://issues.apache.org/jira/browse/HBASE-10514
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.96.2, 0.98.1, 0.99.0, 0.94.18
>
>         Attachments: 10514.txt, 10514v2.txt, 10514v3.txt, 10514v3.txt, 10514v4.txt
>
>
> Critical data loss issues that we need to ensure are not in branches beyond 0.89fb.  Assigning myself.


--
This message was sent by Atlassian JIRA
(v6.2#6252)