Thank you so much @tjangid . This surely clarifies my doubts. ... View more

Hi @sainivedant41  As a last resort, I used the HBCK2 tool to manually change the state of the regions (from CLOSING to CLOSED). The supporting link is mentioned in this thread. You can try it out as well. ... View more

Thank you for the reply @smdas  I checked the Master Logs for the region in question and got this: It mentions the table involved. Do we need to do something with this table? Disable it or something? ... View more

@smdas  Also from the HBase UI, the regions are in CLOSING state: ... View more

Hi @smdas , The commands are mostly in the WAITING state: For the first Id, 1011134 RegionServer A logs: Region Server B logs: Both logs have similar errors and they are recurring too. Does this help? Thanks! ... View more

Thank you for the prompt reply @smdas ! When I run hbase hbck, it shows a lot of inconsistencies and two types of errors: ERROR: Region { meta => CEMSample.pmebktidx,\xCF\x91L\x1B\xAC\xF9\x14\x9A,1602711756619.f99b0dd33f79a9320f3d1e0e663b2498., hdfs => hdfs://BIGMATCHTEST/apps/hbase/data/data/default/CEMSample.pmebktidx/f99b0dd33f79a9320f3d1e0e663b2498, deployed => , replicaId => 0 } not deployed on any region server. ERROR: There is a hole in the region chain between \x0B\xA2\xE8\xBA.\x8B\xA2\xE8 and \x0C\xED\xE6$3\xB7\x98\x90. You need to create a new .regioninfo and region dir in hdfs to plug the hole. I tried assigning the regions manually from the hbase shell but it's either taking a lot of time or getting hung up. What should be done to decrease the Regions in transition? Thanks! ... View more