hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7869) Provide way to not start LogSyncer thread
Date Thu, 21 Feb 2013 07:20:26 GMT

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

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

That works.

In light of this, do you still want to do this? Maybe for your use case it is better to temporarily
block the syncer thread from syncing in the background?
I'm not opposed, just asking.

                
> 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

Mime
View raw message