hbase

History

Nick Dimiduk 0224dccdb8 HBASE-24360 RollingBatchRestartRsAction loses track of dead servers `RollingBatchRestartRsAction` doesn't handle failure cases when tracking its list of dead servers. The original author believed that a failure to restart would result in a retry. However, by removing the dead server from the failed list, that state is lost, and retry never occurs. Because this action doesn't ever look back to the current state of the cluster, relying only on its local state for the current action invocation, it never realizes the abandoned server is still dead. Instead, be more careful to only remove the dead server from the list when the `startRs` invocation claims to have been successful. Signed-off-by: stack <stack@apache.org> (cherry picked from commit `0dae377f53`)	2020-06-22 10:29:09 -07:00
..
src/test	HBASE-24360 RollingBatchRestartRsAction loses track of dead servers	2020-06-22 10:29:09 -07:00
pom.xml	Set version on branch-1 to 1.7.0-SNAPSHOT	2020-02-14 11:31:32 -08:00

Nick Dimiduk 0224dccdb8 HBASE-24360 RollingBatchRestartRsAction loses track of dead servers

`RollingBatchRestartRsAction` doesn't handle failure cases when
tracking its list of dead servers. The original author believed that a
failure to restart would result in a retry. However, by removing the
dead server from the failed list, that state is lost, and retry never
occurs. Because this action doesn't ever look back to the current
state of the cluster, relying only on its local state for the current
action invocation, it never realizes the abandoned server is still
dead. Instead, be more careful to only remove the dead server from the
list when the `startRs` invocation claims to have been successful.

Signed-off-by: stack <stack@apache.org>
(cherry picked from commit 0dae377f53)

2020-06-22 10:29:09 -07:00

src/test HBASE-24360 RollingBatchRestartRsAction loses track of dead servers 2020-06-22 10:29:09 -07:00

pom.xml Set version on branch-1 to 1.7.0-SNAPSHOT 2020-02-14 11:31:32 -08:00