You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Y. SREENIVASULU REDDY (JIRA)" <ji...@apache.org> on 2013/07/23 12:02:50 UTC
[jira] [Updated] (HBASE-9026) RestartRsHoldingRoot action in
org.apache.hadoop.hbase.util.ChaosMonkey restarting the server holding
.META. instead of -ROOT-
[ https://issues.apache.org/jira/browse/HBASE-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Y. SREENIVASULU REDDY updated HBASE-9026:
-----------------------------------------
Description:
In ChaosMonkey instead of restarting Root holded regionServer it is restarting META holded regionServer.
{code}
public static class RestartRsHoldingRoot extends RestartRandomRs {
public RestartRsHoldingRoot(long sleepTime) {
super(sleepTime);
}
@Override
void perform() throws Exception {
LOG.info("Performing action: Restart region server holding ROOT");
ServerName server = cluster.getServerHoldingMeta();
if (server == null) {
LOG.warn("No server is holding -ROOT- right now.");
return;
}
restartRs(server, sleepTime);
}
}
{code}
{noformat}
13/07/23 17:03:54 INFO util.ChaosMonkey: Performing action: Restart region server holding ROOT
13/07/23 17:03:54 DEBUG client.HConnectionManager$HConnectionImplementation: Looked up root region location, connection=org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@52b57e9a; serverName=ocean06,60020,1374569995361
13/07/23 17:03:54 DEBUG client.HConnectionManager$HConnectionImplementation: Removed .META.,,1.1028785192 for tableName=.META. from cache because of
13/07/23 17:03:54 DEBUG client.HConnectionManager$HConnectionImplementation: Cached location for .META.,,1.1028785192 is ocean06:60020
13/07/23 17:03:54 INFO util.ChaosMonkey: Killing region server:ocean06,60020,1374569995361
13/07/23 17:03:54 INFO hbase.HBaseCluster: Aborting RS: ocean06,60020,1374569995361
13/07/23 17:03:54 INFO hbase.ClusterManager: Executing remote command: ps ux | grep regionserver | grep hbase | grep -v grep | tr -s ' ' | cut -d ' ' -f2 | xargs kill -s SIGKILL , hostname:ocean06
13/07/23 17:03:54 INFO util.Shell: Executing full command [/usr/bin/ssh ocean06 "ps ux | grep regionserver | grep hbase | grep -v grep | tr -s ' ' | cut -d ' ' -f2 | xargs kill -s SIGKILL"]
13/07/23 17:03:54 INFO hbase.ClusterManager: Executed remote command, exit code:0 , output:
13/07/23 17:03:54 INFO hbase.HBaseCluster: Waiting service:regionserver to stop: ocean06,60020,1374569995361
13/07/23 17:03:54 INFO hbase.ClusterManager: Executing remote command: ps ux | grep regionserver | grep hbase | grep -v grep | tr -s ' ' | cut -d ' ' -f2 , hostname:ocean06
13/07/23 17:03:54 INFO util.Shell: Executing full command [/usr/bin/ssh ocean06 "ps ux | grep regionserver | grep hbase | grep -v grep | tr -s ' ' | cut -d ' ' -f2"]
13/07/23 17:03:55 INFO hbase.ClusterManager: Executed remote command, exit code:0 , output:
13/07/23 17:03:55 INFO util.ChaosMonkey: Killed region server:ocean06,60020,1374569995361. Reported num of rs:2
{noformat}
This is only in 0.94.X
Affects Version/s: 0.94.8
> RestartRsHoldingRoot action in org.apache.hadoop.hbase.util.ChaosMonkey restarting the server holding .META. instead of -ROOT-
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-9026
> URL: https://issues.apache.org/jira/browse/HBASE-9026
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.8
> Reporter: Y. SREENIVASULU REDDY
> Priority: Minor
>
> In ChaosMonkey instead of restarting Root holded regionServer it is restarting META holded regionServer.
> {code}
> public static class RestartRsHoldingRoot extends RestartRandomRs {
> public RestartRsHoldingRoot(long sleepTime) {
> super(sleepTime);
> }
> @Override
> void perform() throws Exception {
> LOG.info("Performing action: Restart region server holding ROOT");
> ServerName server = cluster.getServerHoldingMeta();
> if (server == null) {
> LOG.warn("No server is holding -ROOT- right now.");
> return;
> }
> restartRs(server, sleepTime);
> }
> }
> {code}
> {noformat}
> 13/07/23 17:03:54 INFO util.ChaosMonkey: Performing action: Restart region server holding ROOT
> 13/07/23 17:03:54 DEBUG client.HConnectionManager$HConnectionImplementation: Looked up root region location, connection=org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@52b57e9a; serverName=ocean06,60020,1374569995361
> 13/07/23 17:03:54 DEBUG client.HConnectionManager$HConnectionImplementation: Removed .META.,,1.1028785192 for tableName=.META. from cache because of
> 13/07/23 17:03:54 DEBUG client.HConnectionManager$HConnectionImplementation: Cached location for .META.,,1.1028785192 is ocean06:60020
> 13/07/23 17:03:54 INFO util.ChaosMonkey: Killing region server:ocean06,60020,1374569995361
> 13/07/23 17:03:54 INFO hbase.HBaseCluster: Aborting RS: ocean06,60020,1374569995361
> 13/07/23 17:03:54 INFO hbase.ClusterManager: Executing remote command: ps ux | grep regionserver | grep hbase | grep -v grep | tr -s ' ' | cut -d ' ' -f2 | xargs kill -s SIGKILL , hostname:ocean06
> 13/07/23 17:03:54 INFO util.Shell: Executing full command [/usr/bin/ssh ocean06 "ps ux | grep regionserver | grep hbase | grep -v grep | tr -s ' ' | cut -d ' ' -f2 | xargs kill -s SIGKILL"]
> 13/07/23 17:03:54 INFO hbase.ClusterManager: Executed remote command, exit code:0 , output:
> 13/07/23 17:03:54 INFO hbase.HBaseCluster: Waiting service:regionserver to stop: ocean06,60020,1374569995361
> 13/07/23 17:03:54 INFO hbase.ClusterManager: Executing remote command: ps ux | grep regionserver | grep hbase | grep -v grep | tr -s ' ' | cut -d ' ' -f2 , hostname:ocean06
> 13/07/23 17:03:54 INFO util.Shell: Executing full command [/usr/bin/ssh ocean06 "ps ux | grep regionserver | grep hbase | grep -v grep | tr -s ' ' | cut -d ' ' -f2"]
> 13/07/23 17:03:55 INFO hbase.ClusterManager: Executed remote command, exit code:0 , output:
> 13/07/23 17:03:55 INFO util.ChaosMonkey: Killed region server:ocean06,60020,1374569995361. Reported num of rs:2
> {noformat}
> This is only in 0.94.X
--
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