Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 21 Feb 2013 06:44:12 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12632784.1361165243630.315833.1361429052938@arcas>
In-Reply-To: <JIRA.12632784.1361165243630@arcas>
References: <JIRA.12632784.1361165243630@arcas>
Subject: [jira] [Commented] (HBASE-7869) Provide way to not start LogSyncer
 thread
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lars Hofhansl commented on HBASE-7869:
--------------------------------------

That maybe true for your usecase, but generally if you disable the syncer and have a table setup with deferred log flush, all regions for that table located on this region server would potentially never flush their logs (possibly for days or weeks).

                
> Provide way to not start LogSyncer thread
> -----------------------------------------
>
>                 Key: HBASE-7869
>                 URL: https://issues.apache.org/jira/browse/HBASE-7869
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver, wal
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 0.96.0, 0.94.6
>
>         Attachments: HBASE-7869_Trunk.patch
>
>
> In our usecase we want all the Mutations on all the tables to be immediately written and synced to WAL. We dont want the LogSyncer thread to be running in such a case.
> In minbatch operation we write entries to WAL and we use postWALWrite and write some more WAL entries(Only write no sync). We want all these written data to be synced as one unit (at the sync step in doMiniBatchOperation) But if the LogSyncer thread is running in the system it can come and do the sync at any point in time which we dont want in our case.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira