anchor.diff:  [source]
   2016-01-08 16:08:57,888 ERROR [pool-26-thread-1-SendThread(localhost:2181)] o.a.zookeeper.client.ZooKeeperSaslClient An error: (java.security.PrivilegedActionException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7) - LOOKING_UP_SERVER)]) occurred when evaluating Zookeeper Quorum Member's  received SASL token. Zookeeper Client will go to AUTH_FAILED state.
   
  -If there are problems communicating or authenticating with Kerberos, 
  +If there are problems communicating or authenticating with Kerberos,
   link:http://docs.oracle.com/javase/7/docs/technotes/guides/security/jgss/tutorials/Troubleshooting.html[this Troubleshooting Guide] may be of value.
   
   One of the most important notes in the above Troubleshooting guide is the mechanism for turning on Debug output for Kerberos.
  
positive.code: 
  
  
  [[state_management]]
  State Management
  ----------------
  
negative.code: 
  This will cause the debug output to be written to the NiFi Bootstrap log file. By default, this is located at _$NIFI_HOME/logs/nifi-bootstrap.log_.
  This output can be rather verbose but provides extremely valuable information for troubleshooting Kerberos failures.
  
  
  
  