[
https://issues.apache.org/jira/browse/HBASE-7869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593180#comment-13593180
]
Hudson commented on HBASE-7869:
-------------------------------
Integrated in HBase-0.94-security-on-Hadoop-23 #12 (See
[https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/12/])
HBASE-7869 Provide way to not start LogSyncer thread (Anoop) (Revision
1451420)
Result = FAILURE
larsh :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLog.java
> 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
> Affects Versions: 0.95.0, 0.94.6
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Fix For: 0.95.0, 0.98.0, 0.94.6
>
> Attachments: HBASE-7869_94.patch, HBASE-7869_Trunk.patch,
> HBASE-7869_Trunk-V2.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
