kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jkr...@apache.org
Subject svn commit: r1574703 - /kafka/site/081/quickstart.html
Date Wed, 05 Mar 2014 22:39:27 GMT
Author: jkreps
Date: Wed Mar  5 22:39:27 2014
New Revision: 1574703

URL: http://svn.apache.org/r1574703
Fix formatting problems in quickstart.


Modified: kafka/site/081/quickstart.html
URL: http://svn.apache.org/viewvc/kafka/site/081/quickstart.html?rev=1574703&r1=1574702&r2=1574703&view=diff
--- kafka/site/081/quickstart.html (original)
+++ kafka/site/081/quickstart.html Wed Mar  5 22:39:27 2014
@@ -5,11 +5,11 @@
 <a href="../downloads.html" title="Kafka downloads">Download</a> the 0.8 release.
-<b>&gt; tar xzf kafka-&lt;VERSION&gt;.tgz</b>
-<b>&gt; cd kafka-&lt;VERSION&gt;</b>
-<b>&gt; ./sbt update</b>
-<b>&gt; ./sbt package</b>
-<b>&gt; ./sbt assembly-package-dependency</b>
+&gt; <b>tar xzf kafka-&lt;VERSION&gt;.tgz</b>
+&gt; <b>cd kafka-&lt;VERSION&gt;</b>
+&gt; <b>./sbt update</b>
+&gt; <b>./sbt package</b>
+&gt; <b>./sbt assembly-package-dependency</b>
 This tutorial assumes you are starting on a fresh ZooKeeper instance and Kafka server with
no pre-existing data.
@@ -20,14 +20,14 @@ This tutorial assumes you are starting o
 Kafka uses zookeeper so you need to first start a zookeeper server if you don't already have
one. You can use the convenience script packaged with kafka to get a quick-and-dirty single-node
zookeeper instance.
-<b>&gt; bin/zookeeper-server-start.sh config/zookeeper.properties</b>
+&gt; <b>bin/zookeeper-server-start.sh config/zookeeper.properties</b>
 [2013-04-22 15:01:37,495] INFO Reading configuration from: config/zookeeper.properties (org.apache.zookeeper.server.quorum.QuorumPeerConfig)
 Now start the Kafka server:
-<b>&gt; bin/kafka-server-start.sh config/server.properties</b>
+&gt; <b>bin/kafka-server-start.sh config/server.properties</b>
 [2013-04-22 15:01:47,028] INFO Verifying properties (kafka.utils.VerifiableProperties)
 [2013-04-22 15:01:47,051] INFO Property socket.send.buffer.bytes is overridden to 1048576
@@ -55,8 +55,8 @@ Run the producer and then type a few mes
 &gt; <b>bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test</b>

-This is a message
-This is another message
+<b>This is a message</a>
+<b>This is another message</b>
 <h4>Step 5: Start a consumer</h4>
@@ -64,7 +64,7 @@ This is another message
 Kafka also has a command line consumer that will dump out messages to standard output.
-<b>&gt; bin/kafka-console-consumer.sh --zookeeper localhost:2181 --topic test --from-beginning</b>
+&gt; <b>bin/kafka-console-consumer.sh --zookeeper localhost:2181 --topic test --from-beginning</b>
 This is a message
 This is another message
@@ -81,8 +81,8 @@ So far we have been running against a si
 First we make a config file for each of the brokers:
-<b>&gt; cp config/server.properties config/server-1.properties 
-&gt; cp config/server.properties config/server-2.properties</b>
+&gt; <b>cp config/server.properties config/server-1.properties</b> 
+&gt; <b>cp config/server.properties config/server-2.properties</b>
 Now edit these new files and set the following properties:
@@ -102,9 +102,9 @@ The <code>broker.id</code> property is t
 We already have Zookeeper and our single node started, so we just need to start the two new
-<b>&gt; bin/kafka-server-start.sh config/server-1.properties &amp;</b>
+&gt; <b>bin/kafka-server-start.sh config/server-1.properties &amp;</b>
-<b>&gt; bin/kafka-server-start.sh config/server-2.properties &amp;</b>
+&gt; <b>bin/kafka-server-start.sh config/server-2.properties &amp;</b>
@@ -143,9 +143,9 @@ Let's publish a few messages to our new 
 <b>my test message 2</b>
-Now consume this message:
+Now let's consume these messages:
-<b>&gt; bin/kafka-console-consumer.sh --zookeeper localhost:2181 --from-beginning
--topic my-replicated-topic</b>
+&gt; <b>bin/kafka-console-consumer.sh --zookeeper localhost:2181 --from-beginning
--topic my-replicated-topic</b>
 my test message 1
 my test message 2
@@ -161,13 +161,13 @@ Now let's test out fault-tolerance. Brok
 Leadership has switched to one of the slaves and node 1 is no longer in the in-sync replica
-&gt; <b>bin/kafktopics.sh --describe --zookeeper localhost:218192 --topic my-replicated-topic</b>
+&gt; <b>bin/kafka-topics.sh --describe --zookeeper localhost:218192 --topic my-replicated-topic</b>
 Topic:my-replicated-topic	PartitionCount:1	ReplicationFactor:3	Configs:
 	Topic: my-replicated-topic	Partition: 0	Leader: 2	Replicas: 1,2,0	Isr: 2,0
 But the messages are still be available for consumption even though the leader that took
the writes originally is down:
-<b>&gt; bin/kafka-console-consumer.sh --zookeeper localhost:2181 --from-beginning
--topic my-replicated-topic</b>
+&gt; <b>bin/kafka-console-consumer.sh --zookeeper localhost:2181 --from-beginning
--topic my-replicated-topic</b>
 my test message 1
 my test message 2

View raw message