WIP: Instant kraft demo #1124
WIP: Instant kraft demo #1124
Conversation
addisonhuddy
requested review from
benstopford,
ijuma,
joel-hamill and
MichaelDrogalis
| $ docker compose exec broker kafka-topics --create --topic zookeeper-vacation-ideas --bootstrap-server localhost:9092 | ||
|
|
||
| $ docker-compose exec broker kafka-producer-perf-test --topic zookeeper-vacation-ideas \ |
There was a problem hiding this comment.
Commands used include both docker compose and docker-compose. The former I think relies on later versions of Docker with either Compose included, or via a command-plugins capability.
Maybe we should stick to one. I think our formal docs lean towards docker-compose.
| ``` | ||
| $ git clone https://github.com/confluentinc/examples.git && cd examples/instant-kraft | ||
|
|
||
| $ docker compose up |
There was a problem hiding this comment.
For better or worse, our examples seem to usually use docker-compose up -d, i.e. launch detached/daemonized, so the current shell isn't left bound to the command and tailing the logs. Downside is that you have to docker logs or docker-compose logs to see any errors or interesting logging.
Up to you whether you want the -d here, but note that users might struggle with losing their shell prompt, and also unintentionally kill with CTRL-C.
|
|
||
| >> cat metadataQuorum/leader | ||
| ``` | ||
|
|
There was a problem hiding this comment.
Should we mention CTRL-D to exit the REPL?
| $ docker compose up | ||
| ``` | ||
|
|
||
| That's it! One container, one process, doing the the broker and controller work. No Zookeeper. |
There was a problem hiding this comment.
I think ZooKeeper (camel case) is standard.
| ___ | ||
| .'O o'-._ | ||
| / O o_.-`| | ||
| /O_.-' O | | ||
| |O o O .-` | ||
| |o O_.-' | ||
| '--` |
There was a problem hiding this comment.
Might need to be in a code block to appear proper cheesy.
| ``` | ||
|
|
||
| ## Step 3 | ||
| Explore the cluster using the new kafka metadata command line tool. |
There was a problem hiding this comment.
Should we refer to it inline by name? I don't mind, just asking: kafka-metadata-shell
| $ docker compose up | ||
| ``` | ||
|
|
||
| That's it! One container, one process, doing the the broker and controller work. No Zookeeper. |
There was a problem hiding this comment.
doing the the broker and controller work
Remove duplicate "the" and reword. Maybe
One container, one process performing both broker and controller/quorum roles.
| ``` | ||
|
|
||
| That's it! One container, one process, doing the the broker and controller work. No Zookeeper. | ||
| The key server configure to enable KRaft is the `process.roles`. Here we have the same node doing both the broker and quorum conroller work. Note that this is ok for local development, but in production you should have seperate nodes for the broker and controller quorum nodes. |
There was a problem hiding this comment.
Needs rewording.
The key server configuration for enabling KRaft is process.roles.
|
@addisonhuddy fyi moved this back to "draft" mode to avoid the stale PR reminders. |
|
|
Creating a single node, lightweight KRaft example that is based on the cp-all-in-one-kraft demo. Over time, this demo will evolve as the KRaft tooling improves. The main goal of the example is to show how easy it is to run Kafka in KRaft mode.
Includes