[
https://issues.apache.org/jira/browse/HBASE-7869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580425#comment-13580425
]
Anoop Sam John commented on HBASE-7869:
---------------------------------------
Suggestion from [~lhofhansl] in HBASE-7801
{quote}
Looking at the code, we could just not start the LogSyncer if
hbase.regionserver.optionallogflushinterval is set to 0. I'd fear there might
be other side effects, but it could just work. But that's for a different jira
anyway.
{quote}
I think it should be safe to add. We will clearly mention that when this is set
as 0 the LogSyncer thread wont be started at all and defered syncing of
Mutation should not be used.
Presence of LogSyncer thread should be optional in the system
> 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
>
> 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
