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 Mon, 18 Feb 2013 05:59:12 GMT

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

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

I suppose there is no harm in disabling the syncer if it's done through a config option.
We can either use hbase.regionserver.optionallogflushinterval=0 or maybe hbase.regionserver.optionallogflushinterval=MAX_INT.
                
> 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
>
>
> 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