# Optimizing Apache HBase availability on Amazon EMR, Part 1: Coordinator startup, RegionServer recovery, and regions in transition

DevFeed: [Optimizing Apache HBase availability on Amazon EMR, Part 1: Coordinator startup, RegionServer recovery, and regions in transition](<https://devfeed.tech/articles/optimizing-apache-hbase-availability-on-amazon-emr-part-1-coordinator-startup-regionserver-recovery-and-regions-in-transition-108403.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/optimizing-apache-hbase-availability-on-amazon-emr-part-1-coordinator-startup-regionserver-recovery-and-regions-in-transition/>)

Author: Reekunj Parmar

Published: 2026-10-29T18:25:48Z

Content type: tutorial

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [Availability](<https://devfeed.tech/topics/availability.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>)

Tags: [amazon-emr](<https://devfeed.tech/tags/amazon-emr.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [apache-zookeeper](<https://devfeed.tech/tags/apache-zookeeper.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws-support](<https://devfeed.tech/tags/aws-support.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [canary](<https://devfeed.tech/tags/canary.md>), [commands](<https://devfeed.tech/tags/commands.md>), [compaction](<https://devfeed.tech/tags/compaction.md>), [hbase](<https://devfeed.tech/tags/hbase.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [log](<https://devfeed.tech/tags/log.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [startup](<https://devfeed.tech/tags/startup.md>), [ui](<https://devfeed.tech/tags/ui.md>), [web](<https://devfeed.tech/tags/web.md>)

## AI overview

The excerpt gives a tiered process for restoring Apache HBase availability on Amazon EMR: start with read-only web UI, shell, and console checks, use logs and resource inspection to identify causes, and reserve state-changing interventions for confirmed problems after taking a snapshot. For a slow HBase coordinator, check HDFS, JVM and GC pauses, ZooKeeper, and--on HBase over Amazon S3--EMRFS throttling; resolve underlying HDFS or ZooKeeper issues before restarting it. For a departed RegionServer, read the coordinator log first, then inspect the server, node health, HDFS, and WAL splitting. For regions stuck in transition, check procedures and locks, report inconsistencies, then use HBCK2 targeted repairs on EMR 6.x/7.x (HBase 2.x); EMR 5.x uses HBCK1 for reporting only. The excerpt warns against HBCK1 repair on HBase 2.x and deleting HBase znodes, and recommends AWS Support if znode clearing seems necessary.

## Source excerpt

A repeatable process for keeping Apache HBase on Amazon EMR highly available. Part 1 covers triaging an HBase coordinator that is slow to start, a RegionServer that leaves the cluster, and regions that stay in transition, with the web UI pages, commands, and log signatures that point to each cause.