Addressed PR comments

Author: vijaysr

articles/hdinsight/spark/zookeeper-troubleshoot-quorum-fails.md

@@ -49,39 +49,68 @@ Message
 * High CPU usage on the zookeeper servers
   * In the Ambari UI, if you see near 100% sustained CPU usage on the zookeeper servers, then the zookeeper sessions open during that time can expire and timeout
 * Zookeeper clients are reporting frequent timeouts
-  * The transaction logs and the snapshots are being written to the same disk. This can cause I/O bottlenecks
+  * In the logs for resource manager, namenode and others, you will see frequent client connection timeouts
+  * This could result in quorum loss, frequent failovers and other issues
 
 ## Check for zookeeper status
   * Find the zookeeper servers from the /etc/hosts file or from Ambari UI
   * Run the following command
     * echo stat | nc {zk_host_ip} 2181 (or 2182)  
-  * Port 2181 is the apache zookeeper instance
-  * Port 2182 is used by the HDI zookeeper (to provide HA for services that are not natively HA)
-
+    * Port 2181 is the apache zookeeper instance
+    * Port 2182 is used by the HDI zookeeper (to provide HA for services that are not natively HA)
+    * If the command shows no output, then it means that the zookeeper servers are not running
+    * If the servers are running, the result will include statics of client connections and other statistics
+````
+Zookeeper version: 3.4.6-8--1, built on 12/05/2019 12:55 GMT
+Clients:
+ /10.2.0.57:50988[1](queued=0,recved=715,sent=715)
+ /10.2.0.57:46632[1](queued=0,recved=138340,sent=138347)
+ /10.2.0.34:14688[1](queued=0,recved=264653,sent=353420)
+ /10.2.0.52:49680[1](queued=0,recved=134812,sent=134814)
+ /10.2.0.57:50614[1](queued=0,recved=19812,sent=19812)
+ /10.2.0.56:35034[1](queued=0,recved=2586,sent=2586)
+ /10.2.0.52:63982[1](queued=0,recved=72215,sent=72217)
+ /10.2.0.57:53024[1](queued=0,recved=19805,sent=19805)
+ /10.2.0.57:45126[1](queued=0,recved=19621,sent=19621)
+ /10.2.0.56:41270[1](queued=0,recved=1348743,sent=1348788)
+ /10.2.0.53:59097[1](queued=0,recved=72215,sent=72217)
+ /10.2.0.56:41088[1](queued=0,recved=788,sent=802)
+ /10.2.0.34:10246[1](queued=0,recved=19575,sent=19575)
+ /10.2.0.56:40944[1](queued=0,recved=717,sent=717)
+ /10.2.0.57:45466[1](queued=0,recved=19861,sent=19861)
+ /10.2.0.57:59634[0](queued=0,recved=1,sent=0)
+ /10.2.0.34:14704[1](queued=0,recved=264622,sent=353355)
+ /10.2.0.57:42244[1](queued=0,recved=49245,sent=49248)
+
+Latency min/avg/max: 0/3/14865
+Received: 238606078
+Sent: 239139381
+Connections: 18
+Outstanding: 0
+Zxid: 0x1004f99be
+Mode: follower
+Node count: 133212
+````
 ## CPU load peaks up every hour
   * Login to the zookeeper server and check the /etc/crontab
   * Are there any hourly jobs running at this time?
   * If so, randomize the start time across different zookeeper servers
 
 ## Purging old snapshots
-  * HDI Zookeepers are configured to auto purge old snapshots
+  * Zookeepers are configured to auto purge old snapshots
   * By default, last 30 snapshots are retained
-  * This controlled by the configuration key autopurge.snapRetainCount
+  * This is controlled by the configuration key autopurge.snapRetainCount
     * /etc/zookeeper/conf/zoo.cfg for hadoop zookeeper
     * /etc/hdinsight-zookeeper/conf/zoo.cfg for HDI zookeeper
-  * Set this to a value =3 and restart the zookeeper servers
-    * Hadoop zookeeper can be restarted through Ambari
+  * Set this to a value of 3 and restart the zookeeper servers
+    * Hadoop zookeeper config can be updated and the service can be restarted through Ambari
     * HDI zookeeper has to be stopped manually and restarted manually
       * sudo lsof -i :2182 will give you the process id to kill
       * sudo python /opt/startup_scripts/startup_hdinsight_zookeeper.py
-  * Manually purging snapshots
-    * **DO NOT delete the snapshot files directly as this could result in data loss**
-      * zookeeper
-        * sudo java -cp /usr/hdp/current/zookeeper-server/zookeeper.jar:/usr/hdp/current/zookeeper-server/lib/* org.apache.zookeeper.server.PurgeTxnLog /hadoop/zookeeper/ /hadoop/zookeeper/ 3
-      * hdinsight-zookeeper
-        * sudo java -cp /usr/hdp/current/zookeeper-server/zookeeper.jar:/usr/hdp/current/zookeeper-server/lib/* org.apache.zookeeper.server.PurgeTxnLog /hadoop/hdinsight-zookeeper/ /hadoop/hdinsight-zookeeper/ 3
-        
-## CancelledKeyException in the zookeeper server log
+  * Manually purging snapshots is not required
+    * **DO NOT delete the snapshot files directly as this could result in data loss**    
+    
+## CancelledKeyException in the zookeeper server log doesn't require snapshot cleanup
   * This exception usually means that the client is no longer active and the server is unable to send a message
   * This is indication of a symptom that the zookeeper client is terminating sessions prematurely
   * Look for the other symptoms outlined in this document