[
https://issues.apache.org/jira/browse/AMBARI-24380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated AMBARI-24380:
---------------------------------
Summary: Ambari HBase Rolling Restart failed to check RegionServers started
up successfully, continued to take down rest of RegionServers! (was: Ambari
HBase Rolling Restart failed to check RegionServers came back online properly)
> Ambari HBase Rolling Restart failed to check RegionServers started up
> successfully, continued to take down rest of RegionServers!
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-24380
> URL: https://issues.apache.org/jira/browse/AMBARI-24380
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Hari Sekhon
> Priority: Critical
>
> Ambari rolling-restart of HBase RegionServers failed to detect that
> RegionServers were not coming back online, continued to take down cluster.
> Adding the following JVM tuning setting to HBASE_OPTS in hbase-env.sh
> template near the start of the options:
> {code:java}
> -XX:G1NewSizePercent=3{code}
> before the following option (which was set): a couple options further along
> {code:java}
> -XX:+UnlockExperimentalVMOptions{code}
> resulted in both HMaster and RegionServer startup failures, but Ambari did
> not detect that the RegionServers were not coming back online, and proceeded
> to take out the rest of the RegionServers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
