Hello @snm1523    As the Post was resolved, I am marking the Post as Solved. In future, Kindly mark the Post as Solved to ensure other Community Users can reference the Post for similar issues.   Thanks for using Cloudera Community.    - Smarak ... View more

Hello @rajatsachan    Thanks for using Cloudera Community. Based on the post, You have 2 issues: (I) Region In Transition, (II) HBCK Unavailability in HBase v2.x.    For (I), RIT indicates the Regions are likely in OPENING, FAILED_OPEN, CLOSING, FAILED_CLOSE State. For any Region to move from say, RegionServer A to RegionServer B, the Region is Closed on RegionServer A before being opened on RegionServer B. Depending on the Region State, We need to check either RegionServer A or RegionServer B Logs to identify the reasoning for the Transition. Finally, Your Environment has ~1900 Regions per RegionServer, which is way beyond the general recommendations of 300/400 Regions per RegionServer. Such large Region/RegionServer Count would cause delay in WALSplit + WALEditReplay + RegionClosing or RegionOpening etc.    For (II), KIndly review Link [1]. In short, HBase v2.x requires HBCK v2.x. You can use HBCK1 Read-Only Commands (Example: hbase hbck -details) on HBase v2.x yet any HBCK1 Fix Command won't work on HBase v2.x. You need to use the HBCK v2.x, which has to be built as described in the Link.   - Smarak   [1] https://community.cloudera.com/t5/Community-Articles/HBase-HBCK2-tool-for-HDP-3-x/ta-p/244386 ... View more

Hello @SDL    Thanks for the Update. Based on your comment, I assume the Configuration is being over-written owing to the nightly stop of the instance, which is using the default configuration.    - Smarak ... View more

Hello @snm1523    Signal 15 tells us that something or someone intentionally killed the process. Check the Process StdOut & StdErr file for details.    - Smarak ... View more

Hello @Rjkoop    There are a few things worth trying i.e. Setting "dfs.client.read.shortcircuit" as true for RegionServers + "hbase.wal.provider" as "filesystem" + "hbase.wal.meta_provider" as "filesystem" + dfs.domain.socket.path=<Add Same Value Configured For HDFS>. Restart the HBase Service.    Try performing the HBase PE Test before the above Changes & recheck the HBase PE after the above changes. Do let us know the Outcome.   - Smarak ... View more

Hello @SDL    Thanks for using Cloudera Community. As you have used InfraSolr & HDP tag, Kindly confirm the HDP Version wherein the concerned issue is being observed.    Additionally, Link [1] is an excellent article on the concerned Topic & may offer any missing details.   - Smarak   [1] https://community.cloudera.com/t5/Community-Articles/Solr-TTL-Auto-Purging-Solr-Documents-Ranger-Audits/ta-p/247920 ... View more

Hello @SurajP    Thanks for using Cloudera Community. The Error shows a BindAddress issue on Port 2181. Kindly check whether the Port 2181 is being used by any Process on the Host, wherein the ZooKeeper Service is being started. If Yes, Terminate the Process after reviewing the same & try starting the ZooKeeper Service again.   - Smarak ... View more

Hello @ShamsN    Kindly update the Post, if you have solved the issue. If you continue to face the issue, Let us know & we can assist you. We requested additional details based on your Post on 12/16.    - Smarak ... View more

Hello @ASIF123    Checking whether the concerned issue posted by your team has been resolved. If Yes, Kindly mark the Post as Solved. If No, Kindly review our Post dated 12/18 & share the outcome of the Action Plan shared.   - Smarak ... View more