Wonderful question, too bad noone answered this. We are handling something similar (upgrading to HDP3.1.5 from HDP2.6.5 in diffrent cluster - HBase 1.1.2 to Hbase 2.0.2). We asked this through Cloudera support and offered us same solution - copyTable / syncTable but this can't be run from destination cluster (since the source cluster is in current production) so we're looking at snapshots solution, but we still need to identify if is feasible and the challenges implied...
Any inputs from your experience? did you managed to do this migration/upgrade?
@Ivoz As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks!
Diana Torres, Community Moderator
Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. Learn more about the Cloudera Community:
This is an older post which had a few recent followup queries. To close the loop, HBase offers multiple Tools to migrate Data from 1 Cluster to another Cluster like Snapshot, Export-Import, HashTable/SyncTable etc. Most of these Tools relies on MapReduce & uses 1 Mapper per Region of the Source Table. All these Tools works without any concerns. The only part of the ask which can't be answered accurately is the Concurrency/Job Configurations/Mapper Memory etc. These details rely on Customer's Environment Setup & the Bandwidth between the 2 Clusters. As such, Customer can run 1 such HBase MR Job & see the Outcome. Accordingly, Fine-Tune is required.
If any issues are observed while performing the above HBase MR Job, Feel free to post the Q in a Community Post for fellow Community Members to review & share their thoughts.