anchor.diff:  
   [source,bash]
   ----
  -$ bin/kafka-topics.sh --zookeeper localhost:2181 --create --topic test_topic --partitions 5 --replication-factor 2
  +$ bin/kafka-topics.sh --zookeeper zkhost:2181 --create --topic test_topic --partitions 5 --replication-factor 2
   Created topic "test_topic".
   
  -$ bin/kafka-topics.sh --zookeeper localhost:2181 --describe --topic test_topic
  +$ bin/kafka-topics.sh --zookeeper zkhost:2181 --describe --topic test_topic
   Topic:test_topic        PartitionCount:5        ReplicationFactor:2     Configs:
           Topic: test_topic       Partition: 0    Leader: 1       Replicas: 1,3   Isr: 1,3
           Topic: test_topic       Partition: 1    Leader: 3       Replicas: 3,0   Isr: 3,0
  
positive.code: }
  ----
  
  You should be aware that you can not execute an assignment plan containing a dead or stopped node.
  The assignment can only be execute if brokers
  
  You can check in this assignment plan that:
  
  * All 4 nodes are used,
  * Each node has roughly the number of partitions: 6 or 7 (= (2&times;5 + 3&times;5) &div; 4)
  
  To run this plan, we will use the `kafka-reassign-partitions.sh` tool with the `--execute` command.
  It takes the generated `reassignment.json` file as input.
  
  ----
  $ bin/kafka-reassign-partitions.sh --zookeeper localhost:2181 --execute --reassignment-json-file reassignment.json
  Current partition replica assignment
  
  {"version":1,"partitions":[{"topic":"test_topic","partition":0,"replicas":[2,0]},{"topic":"test_topic","partition":4,"replicas":[0,2]},{"topic":"__consumer_offsets","partition":0,"replicas":[0,3,1]},{"topic":"__consumer_offsets","partition":3,"replicas":[3,2,0]},{"topic":"test_topic","partition":3,"replicas":[2,1]},{"topic":"test_topic","partition":2,"replicas":[1,2]},{"topic":"__consumer_offsets","partition":4,"replicas":[0,1,2]},{"topic":"test_topic","partition":1,"replicas":[0,1]},{"topic":"__consumer_offsets","partition":2,"replicas":[2,1,3]},{"topic":"__consumer_offsets","partition":1,"replicas":[1,0,2]}]}
  
negative.code: == Rack awareness
  
  Starting with version 0.10.0, Kafka supports rack aware replica placement.
  It means Kafka will try to place replicas in different racks (or availability zones).
  
  The only change is the `broker.rack` property in the broker configuration file:
  
  