[jira] [Updated] (HBASE-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-5549: - Fix Version/s: (was: 0.95.0) 0.94.2 Fix up after bulk move overwrote some 0.94.2 fix versions w/ 0.95.0 (Noticed by Lars Hofhansl) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, Zookeeper >Affects Versions: 0.95.2 > Environment: all >Reporter: Nicolas Liochon >Assignee: Nicolas Liochon >Priority: Minor > Fix For: 0.94.2 > > Attachments: 5549_092.txt, 5549_094.txt, 5549.v10.patch, > 5549.v11.patch, 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, 5549.v9.patch, > nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-5549: - Fix Version/s: 0.94.2 Applied to 0.94 branch. > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Fix For: 0.92.2, 0.96.0, 0.94.2 > > Attachments: 5549_092.txt, 5549_094.txt, 5549.v10.patch, > 5549.v11.patch, 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, 5549.v9.patch, > nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-5549: - Attachment: 5549_094.txt Patch for 0.94. Doesn't seem to have broken anything obvious. Will apply and keep an eye out. > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Fix For: 0.92.2, 0.96.0, 0.94.2 > > Attachments: 5549_092.txt, 5549_094.txt, 5549.v10.patch, > 5549.v11.patch, 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, 5549.v9.patch, > nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-5549: - Fix Version/s: 0.92.2 Applied to 0.92 branch. Working on patch for 0.94 now. > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Fix For: 0.92.2, 0.96.0 > > Attachments: 5549_092.txt, 5549.v10.patch, 5549.v11.patch, > 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-5549: - Attachment: 5549_092.txt Backport of the trunk patch to 0.92 > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Fix For: 0.96.0 > > Attachments: 5549_092.txt, 5549.v10.patch, 5549.v11.patch, > 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Yu updated HBASE-5549: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Fix For: 0.96.0 > > Attachments: 5549.v10.patch, 5549.v11.patch, 5549.v6.patch, > 5549.v7.patch, 5549.v8.patch, 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Yu updated HBASE-5549: -- Fix Version/s: 0.96.0 Hadoop Flags: Reviewed Integrated to TRUNK. Thanks for the patch, N. Thanks for the review, Stack. > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Fix For: 0.96.0 > > Attachments: 5549.v10.patch, 5549.v11.patch, 5549.v6.patch, > 5549.v7.patch, 5549.v8.patch, 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Patch Available (was: Open) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v10.patch, 5549.v11.patch, 5549.v6.patch, > 5549.v7.patch, 5549.v8.patch, 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Attachment: 5549.v11.patch > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v10.patch, 5549.v11.patch, 5549.v6.patch, > 5549.v7.patch, 5549.v8.patch, 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Open (was: Patch Available) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v10.patch, 5549.v11.patch, 5549.v6.patch, > 5549.v7.patch, 5549.v8.patch, 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Attachment: 5549.v10.patch > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v10.patch, 5549.v6.patch, 5549.v7.patch, > 5549.v8.patch, 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Patch Available (was: Open) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v10.patch, 5549.v6.patch, 5549.v7.patch, > 5549.v8.patch, 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Open (was: Patch Available) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, > 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Patch Available (was: Open) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, > 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Attachment: 5549.v9.patch > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, > 5549.v9.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Open (was: Patch Available) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, > nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Open (was: Patch Available) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, > nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Attachment: 5549.v8.patch > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, > nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Patch Available (was: Open) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, 5549.v7.patch, 5549.v8.patch, > nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Attachment: 5549.v7.patch > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, 5549.v7.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Patch Available (was: Open) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, 5549.v7.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Open (was: Patch Available) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Attachment: nochange.patch > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Patch Available (was: Open) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch, nochange.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Open (was: Patch Available) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Status: Patch Available (was: Open) > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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-5549) Master can fail if ZooKeeper session expires
[ https://issues.apache.org/jira/browse/HBASE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-5549: --- Attachment: 5549.v6.patch Contains the patch for HBASE-5572 > Master can fail if ZooKeeper session expires > > > Key: HBASE-5549 > URL: https://issues.apache.org/jira/browse/HBASE-5549 > Project: HBase > Issue Type: Bug > Components: master, zookeeper >Affects Versions: 0.96.0 > Environment: all >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 5549.v6.patch > > > There is a retry mechanism in RecoverableZooKeeper, but when the session > expires, the whole ZooKeeperWatcher is recreated, hence the retry mechanism > does not work in this case. This is why a sleep is needed in > TestZooKeeper#testMasterSessionExpired: we need to wait for ZooKeeperWatcher > to be recreated before using the connection. > This can happen in real life, it can happen when: > - master & zookeeper starts > - zookeeper connection is cut > - master enters the retry loop > - in the meantime the session expires > - the network comes back, the session is recreated > - the retries continues, but on the wrong object, hence fails. -- 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
