Hi @Jasthi ,   These are alerts coming from the CM. For more details on those, you can click on specific alerts which can give more clarity as to why the alert is seen.   For more details, you can refer the below doc : https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cm_ht_regionserver.html ... View more

Hi @Meepoljd    As per the description of the issue, I believe you are hitting ZOOKEEPER-1622 . Cloudera has already released TSB-2022-577 for this. As mentioned in the TSB, the session IDs should be unique but due to this bug, two clients might use the same session ID and hence causing the unexpected session termination. ... View more

Hello @KPG1 ,   The time taken to mark a datanode as stale is give by dfs.namenode.stale.datanode.interval, with a default of 30 seconds. If this is happening with a specific Datanode, you can check if there is any network issues between the Datanode and the Namenode or if the Datanode has any JVM pauses reported by checking the Datanode logs. As a bandaid, you can bump up the above parameter till the underlying problem is solved. ... View more