You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2013/09/25 20:36:03 UTC
[jira] [Created] (HBASE-9657) Race condition in low replication
checking and FSHLog#rollWriter()
Ted Yu created HBASE-9657:
-----------------------------
Summary: Race condition in low replication checking and FSHLog#rollWriter()
Key: HBASE-9657
URL: https://issues.apache.org/jira/browse/HBASE-9657
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: 9657-v1.txt
In FSHLog#syncer(), we have this comment:
{code}
// TODO: preserving the old behavior for now, but this check is strange. It's not
// protected by any locks here, so for all we know rolling locks might start
// as soon as we enter the "if". Is this best-effort optimization check?
if (!this.logRollRunning) {
checkLowReplication();
{code}
The implication is that checkLowReplication() may be running when FSHLog#rollWriter() is also running.
--
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