[
https://issues.apache.org/jira/browse/HBASE-7869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582975#comment-13582975
]
Anoop Sam John commented on HBASE-7869:
---------------------------------------
When Mutation is having WriteToWAL as false, deferred sync is out of question
any way.
To address Lars comment
- IMO we should do 1#. Mutation wanted it to be written to WAL. By default the
log syncer thread will be started and here user some how changed the interval
to 0. An interval 0 means need an immediate sync. :)
- During the startup if the value is set as 0 and we don't start a syncer
thread, we will log an INFO saying clearly that deferred syncing wont work with
this RS and all such will be synced immediately.
What do you guys say?
> 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
