Hi Aswini,
Based on my understanding, the issue you've described is that the process of closing an HBase region becomes stuck during compactions. However, I couldn't locate this problem in the attached report. How did you discover that the process was stuck? Did you manage to capture a thread dump during the occurrence of the issue? Did you check the logs of the HBase region server where this issue is occurring?
You can use the open source yCrash script which will capture 360-degree application level artifacts (like GC logs, 3 snapshots of thread dumps, heap dumps) and system level artifacts (like top, top -H, netstat, vmstat, iostat, dmesg, diskusage, kernel parameters...). Once you have these data, either you can manually analyze them or upload it to yCrash tool. Tool analyzes all these dataset and generates an instant root cause analysis report.
Edit your Comment