[ https://issues.apache.org/jira/browse/BOOKKEEPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sijie Guo updated BOOKKEEPER-69: -------------------------------- Fix Version/s: 4.0.0 > ServerRedirectLoopException when a machine (hosts bookie server & hub server) > reboot, which is caused by race condition of topic manager > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: BOOKKEEPER-69 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-69 > Project: Bookkeeper > Issue Type: Bug > Components: hedwig-client, hedwig-server > Affects Versions: 3.4.0 > Environment: 3 machines (perf8, perf9, perf10), each machine hosts a > bookie server & a hub server. > perf8 is used as default server for client 1. perf9 is used as default server > for client 2. > bookkeeper is configured as below: > ensemble size is 3, quorum size is 2. > Reporter: Sijie Guo > Priority: Critical > Fix For: 4.0.0 > > Attachments: bookkeeper-69-testcase.patch, bookkeeper-69.patch > > > 1) machine perf10 is rebooted. the bookie server & hub server are not > restarted automatically after reboot. > 2) client 1 & client 2 are still running. the topics owned in perf10 will be > re-assigned to perf8/perf9. but they would fail because not enough bookie > servers are available. > 3) after 2 hours, we found that perf10 is rebooted. we restarted bookie > server & hub server on perf10 > 4) then we got ServerRedirectLoopException in client. -- 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