title: Getting error while consuming kafka message
body: <p>I am getting below error while I am consuming message from kafka broker, can someone please suggest what I am doing wrong or i am missing, I have put the steps i am following to create a topi , produce a message and then consume the message (FYI this is on HDP 2.5.5, and kafka 0.10.x)</p>
  
  <p>export BK="node1:6667,node1:6667,node1:6667"</p>
  
  <p>export ZK="zk1:2181,zk1:2181,zk1:2181"</p>
  
  <p>Created a topic:
  Kinit to kafka user
  bin/kafka-topics.sh --create --zookeeper zk1:2181,zk1:2181,zk1:2181 --replication-factor 3 --partitions 1 --topic test3</p>
  
  <p>List the topics:
  bin/kafka-topics.sh --list --zookeeper zk1:2181,zk1:2181,zk1:2181 localhost:2181
  Produce a message on a topic:
  bin/kafka-console-producer.sh --broker-list $BK  --topic test3
  I can produce message 
  or with port 9092
  bin/kafka-console-producer.sh --broker-list node1:9092,node2:9092,node2:9092 --topic test3</p>
  
  <p>Consume the message:
  bin/kafka-console-consumer.sh --zookeeper $ZK --bootstrap-server $BK  --topic test3 --from-beginning 
  also tried with –security-protocol PLAINTEXTSASL getting error :
  [2017-06-21 02:09:09,620] WARN Could not login: the client is being asked for a password, but the Zookeeper client code does not currently support obtaining a password from the user. Make sure that the client is configured to use a ticket cache (using the JAAS configuration setting 'useTicketCache=true)' and restart the client. If you still get this message after that, the TGT in the ticket cache has expired and must be manually refreshed. To do so, first determine if you are using a password or a keytab. If the former, run kinit in a Unix shell in the environment of the user who is running this Zookeeper client using the command 'kinit ' (where  is the name of the client's Kerberos principal). If the latter, do 'kinit -k -t  ' (where  is the name of the Kerberos principal, and  is the location of the keytab file). After manually refreshing your cache, restart this client. If you continue to see this message after manually refreshing your cache, ensure that your KDC host's clock is in sync with this host's clock. (org.apache.zookeeper.client.ZooKeeperSaslClient)
  [2017-06-21 02:09:09,622] WARN SASL configuration failed: javax.security.auth.login.LoginException: No password provided Will continue connection to Zookeeper server without SASL authentication, if Zookeeper server allows it. (org.apache.zookeeper.ClientCnxn) No brokers found in ZK.</p>