You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by jg...@apache.org on 2019/05/19 02:57:11 UTC

[kafka] branch trunk updated: MINOR: Update command options for kafka-console-consumer.sh in vagrant/README.md (#6689)

This is an automated email from the ASF dual-hosted git repository.

jgus pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/trunk by this push:
     new fc616cb  MINOR: Update command options for kafka-console-consumer.sh in vagrant/README.md (#6689)
fc616cb is described below

commit fc616cb521c3f7e377b8b0ac65a3a83101156951
Author: Kengo Seki <se...@apache.org>
AuthorDate: Sun May 19 11:56:56 2019 +0900

    MINOR: Update command options for kafka-console-consumer.sh in vagrant/README.md (#6689)
    
    The following command in vagrant/README.md doesn't work,
    since `--zookeeper` option has been unsuppored from v2.0.0.
    This PR updates its command options to fix it.
    
    ```
    bin/kafka-console-consumer.sh --zookeeper zk1:2181 --topic sandbox --from-beginning
    ```
    
    Reviewers: Jason Gustafson <ja...@confluent.io>
---
 vagrant/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/vagrant/README.md b/vagrant/README.md
index f482f04..d844829 100644
--- a/vagrant/README.md
+++ b/vagrant/README.md
@@ -56,8 +56,8 @@ You can access the brokers and zookeeper by their IP or hostname, e.g.
     # Specify brokers by their hostnames: broker1, broker2, broker3
     bin/kafka-console-producer.sh --broker-list broker1:9092,broker2:9092,broker3:9092 --topic sandbox
 
-    # Specify ZooKeeper node by its hostname: zk1
-    bin/kafka-console-consumer.sh --zookeeper zk1:2181 --topic sandbox --from-beginning
+    # Specify brokers by their IP: 192.168.50.51, 192.168.50.52, 192.168.50.53
+    bin/kafka-console-consumer.sh --bootstrap-server 192.168.50.51:9092,192.168.50.52:9092,192.168.50.53:9092 --topic sandbox --from-beginning
 
 If you need to update the running cluster, you can re-run the provisioner (the
 step that installs software and configures services):