You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars George (JIRA)" <ji...@apache.org> on 2011/02/14 19:05:57 UTC
[jira] Created: (HBASE-3530) Do not start LogSyncer when not in
deferred flush mode
Do not start LogSyncer when not in deferred flush mode
------------------------------------------------------
Key: HBASE-3530
URL: https://issues.apache.org/jira/browse/HBASE-3530
Project: HBase
Issue Type: Improvement
Components: regionserver
Affects Versions: 0.90.0
Reporter: Lars George
Priority: Minor
Fix For: 0.92.0
Currently we always start the LogSyncer thread, even when not necessary because the "deferred flush" is set to false and the sync() is called on every record. We could disable the thread and not have it flush every n secs unnecessarily.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HBASE-3530) Do not start LogSyncer when not in
deferred flush mode
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994471#comment-12994471 ]
Lars George commented on HBASE-3530:
------------------------------------
We better wait then and see what you've got. Love the improvements done recently in this area.
> Do not start LogSyncer when not in deferred flush mode
> ------------------------------------------------------
>
> Key: HBASE-3530
> URL: https://issues.apache.org/jira/browse/HBASE-3530
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.90.0
> Reporter: Lars George
> Priority: Minor
> Fix For: 0.92.0
>
>
> Currently we always start the LogSyncer thread, even when not necessary because the "deferred flush" is set to false and the sync() is called on every record. We could disable the thread and not have it flush every n secs unnecessarily.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HBASE-3530) Do not start LogSyncer when not in
deferred flush mode
Posted by "Jonathan Gray (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994399#comment-12994399 ]
Jonathan Gray commented on HBASE-3530:
--------------------------------------
In some of the HLog improvements that Dhruba and I have been working on, we've become dependent on the LogSyncer thread. However, this is also still using an HBase-side group commit. Just an FYI (alternative implementations of HLog might be a neat idea, there are lots of different ways to optimize depending on the use case)... don't let it hold you up.
Expect some patches this week around this stuff. Currently tracking down a pesky race condition.
> Do not start LogSyncer when not in deferred flush mode
> ------------------------------------------------------
>
> Key: HBASE-3530
> URL: https://issues.apache.org/jira/browse/HBASE-3530
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.90.0
> Reporter: Lars George
> Priority: Minor
> Fix For: 0.92.0
>
>
> Currently we always start the LogSyncer thread, even when not necessary because the "deferred flush" is set to false and the sync() is called on every record. We could disable the thread and not have it flush every n secs unnecessarily.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira