Migration of Hbase Running on EMR | TO THE NEW Blog

We can process huge amounts of data for analytics purposes and business intelligence workloads with help of this framework. Please verify ebs volume size from the old cluster nodes and map it accordingly. We faced the issue while importing big hbase table snapshots (size > 30 GB) from s3. After debugging we got two solutions for this problem: • None Use mapper in command which import snapshot from s3 • None Check volume attached to EMR nodes and increase the number of nodes if required. So, in order to avoid mismatch of count and size some downtime required.