[
https://issues.apache.org/jira/browse/HBASE-7869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580427#comment-13580427
]
Lars Hofhansl commented on HBASE-7869:
--------------------------------------
The problem with this approach is that in that case you cannot place any region
of a table declared with deferred flush on this region server. I still think
disabling the logSyncer altogether is a risky proposition.
One could also introduce a "deferred sync lock" (or maybe use one of the
existing lock) to prevent the background thread from syncing when that would
interfere with the logic.
Generally edits that need to be applied atomically should be added to same
WALEdit.
> 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
