[jira] [Updated] (HBASE-5890) SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS
[ https://issues.apache.org/jira/browse/HBASE-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-5890: -- Status: Open (was: Patch Available) SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS Key: HBASE-5890 URL: https://issues.apache.org/jira/browse/HBASE-5890 Project: HBase Issue Type: Bug Reporter: Nicolas Spiegelberg Priority: Minor Attachments: HBASE-5890.patch We ran into a production issue yesterday where the SplitLogManager tried to create a Rescan node in ZK. The createAsync() generated a KeeperException.CONNECTIONLOSS that was immedately sent to processResult(), createRescan node with --retry_count was called, and this created a CPU busywait that also clogged up the logs. We should handle this better. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-5890) SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS
[ https://issues.apache.org/jira/browse/HBASE-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-5890: - Fix Version/s: (was: 0.95.0) Moving out of 0.95. Issue has merit but no assignee and good suggestions on how the patch could be improved. SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS Key: HBASE-5890 URL: https://issues.apache.org/jira/browse/HBASE-5890 Project: HBase Issue Type: Bug Reporter: Nicolas Spiegelberg Priority: Minor Attachments: HBASE-5890.patch We ran into a production issue yesterday where the SplitLogManager tried to create a Rescan node in ZK. The createAsync() generated a KeeperException.CONNECTIONLOSS that was immedately sent to processResult(), createRescan node with --retry_count was called, and this created a CPU busywait that also clogged up the logs. We should handle this better. -- 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
[jira] [Updated] (HBASE-5890) SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS
[ https://issues.apache.org/jira/browse/HBASE-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-5890: - Fix Version/s: (was: 0.94.1) 0.94.2 And on to 0.94.2 SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS Key: HBASE-5890 URL: https://issues.apache.org/jira/browse/HBASE-5890 Project: HBase Issue Type: Bug Reporter: Nicolas Spiegelberg Priority: Minor Fix For: 0.96.0, 0.89-fb, 0.94.2 Attachments: HBASE-5890.patch We ran into a production issue yesterday where the SplitLogManager tried to create a Rescan node in ZK. The createAsync() generated a KeeperException.CONNECTIONLOSS that was immedately sent to processResult(), createRescan node with --retry_count was called, and this created a CPU busywait that also clogged up the logs. We should handle this better. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5890) SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS
[ https://issues.apache.org/jira/browse/HBASE-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-5890: - Fix Version/s: (was: 0.94.0) 0.94.1 Moving out for now. SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS Key: HBASE-5890 URL: https://issues.apache.org/jira/browse/HBASE-5890 Project: HBase Issue Type: Bug Reporter: Nicolas Spiegelberg Priority: Minor Fix For: 0.96.0, 0.89-fb, 0.94.1 Attachments: HBASE-5890.patch We ran into a production issue yesterday where the SplitLogManager tried to create a Rescan node in ZK. The createAsync() generated a KeeperException.CONNECTIONLOSS that was immedately sent to processResult(), createRescan node with --retry_count was called, and this created a CPU busywait that also clogged up the logs. We should handle this better. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5890) SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS
[ https://issues.apache.org/jira/browse/HBASE-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Spiegelberg updated HBASE-5890: --- Attachment: HBASE-5890.patch patch should work for 89fb, 94, and trunk SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS Key: HBASE-5890 URL: https://issues.apache.org/jira/browse/HBASE-5890 Project: HBase Issue Type: Bug Reporter: Nicolas Spiegelberg Priority: Minor Fix For: 0.94.0, 0.96.0, 0.89-fb Attachments: HBASE-5890.patch We ran into a production issue yesterday where the SplitLogManager tried to create a Rescan node in ZK. The createAsync() generated a KeeperException.CONNECTIONLOSS that was immedately sent to processResult(), createRescan node with --retry_count was called, and this created a CPU busywait that also clogged up the logs. We should handle this better. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5890) SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS
[ https://issues.apache.org/jira/browse/HBASE-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Spiegelberg updated HBASE-5890: --- Fix Version/s: 0.89-fb 0.96.0 0.94.0 Status: Patch Available (was: Open) SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS Key: HBASE-5890 URL: https://issues.apache.org/jira/browse/HBASE-5890 Project: HBase Issue Type: Bug Reporter: Nicolas Spiegelberg Priority: Minor Fix For: 0.94.0, 0.96.0, 0.89-fb Attachments: HBASE-5890.patch We ran into a production issue yesterday where the SplitLogManager tried to create a Rescan node in ZK. The createAsync() generated a KeeperException.CONNECTIONLOSS that was immedately sent to processResult(), createRescan node with --retry_count was called, and this created a CPU busywait that also clogged up the logs. We should handle this better. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
