You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/main/asciidoc/_chapters/ops_mgt.adoc
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1364,9 +1364,10 @@ Copy the script if you need to make use of it in a version of hbase previous to
1364
1364
1365
1365
A downside to the above stop of a RegionServer is that regions could be offline for a good period of time.
1366
1366
Regions are closed in order.
1367
-
If many regions on the server, the first region to close may not be back online until all regions close and
1368
-
after the master notices the RegionServer's znode gone. A node can be asked to gradually shed its load and
1369
-
then shutdown itself using the _graceful_stop.sh_ script. Here is its usage:
1367
+
If many regions on the server, the first region to close may not be back online until all regions close and after the master notices the RegionServer's znode gone.
1368
+
In Apache HBase 0.90.2, we added facility for having a node gradually shed its load and then shutdown itself down.
1369
+
Apache HBase 0.90.2 added the _graceful_stop.sh_ script.
1370
+
Here is its usage:
1370
1371
1371
1372
----
1372
1373
$ ./bin/graceful_stop.sh
@@ -1392,17 +1393,16 @@ To decommission a loaded RegionServer, run the following: +$
1392
1393
[NOTE]
1393
1394
====
1394
1395
The `HOSTNAME` passed to _graceful_stop.sh_ must match the hostname that hbase is using to identify RegionServers.
1395
-
HBase uses fully-qualified domain names usually. Check the list of RegionServers in the master UI for how HBase
1396
-
is referring to servers. Whatever HBase is using, this is what you should pass the _graceful_stop.sh_ decommission script.
1397
-
If you pass IPs, the script is not yet smart enough to make a hostname (or FQDN) of it and so it will fail when it checks
1398
-
if server is currently running; the graceful unloading of regions will not run.
1396
+
Check the list of RegionServers in the master UI for how HBase is referring to servers.
1397
+
It's usually hostname but can also be FQDN.
1398
+
Whatever HBase is using, this is what you should pass the _graceful_stop.sh_ decommission script.
1399
+
If you pass IPs, the script is not yet smart enough to make a hostname (or FQDN) of it and so it will fail when it checks if server is currently running; the graceful unloading of regions will not run.
1399
1400
====
1400
1401
1401
1402
The _graceful_stop.sh_ script will move the regions off the decommissioned RegionServer one at a time to minimize region churn.
1402
-
It will verify the region deployed in the new location before it will moves the next region and so on until the decommissioned
1403
-
server is carrying zero regions. At this point, the _graceful_stop.sh_ tells the RegionServer `stop`.
1404
-
The master will at this point notice the RegionServer gone but all regions will have already been redeployed and because the
1405
-
RegionServer went down cleanly, there will be no WAL logs to split.
1403
+
It will verify the region deployed in the new location before it will moves the next region and so on until the decommissioned server is carrying zero regions.
1404
+
At this point, the _graceful_stop.sh_ tells the RegionServer `stop`.
1405
+
The master will at this point notice the RegionServer gone but all regions will have already been redeployed and because the RegionServer went down cleanly, there will be no WAL logs to split.
0 commit comments