You’ll verify that the broker is functioning normally by creating a topic and producing data to it. Now you can take this basic deployment for a test drive. Test the broker by following these instructions. Kafka_1 | INFO : Started partition state machine with initial state -> Map () ( ) Kafka_1 | INFO : Started replica state machine with initial state -> Map () ( ) Kafka_1 | INFO, Started 1 acceptor threads ( ) If you are running on Mac or Windows, be sure to allocate at least 4 GB of RAM to the Docker Machine. Docker runs natively on Linux, so the Docker host will be your local machine if you go that route.
If you’re running on Windows or macOS, you’ll need to use Docker Machine to start the Docker host. Mounted volumes provide a persistent storage layer for deployed containers, which allows images such as cp-kafka and cp-zookeeper to be stopped and restarted without losing their stateful data. You should refer to the documentation on Docker external volumes for examples of how to add mounted volumes to your host machines. You will also be configuring Kafka and ZooKeeper to store data locally in their Docker containers. Details on more complex target environments are available later in this documentation ( More Tutorials). To keep things simple, you can start with a single node Docker environment.
By the end of this quickstart, you will have a functional Confluent deployment against which you can run any number of applications. So far everything is fine.This quick start provides a basic guide for deploying a Kafka cluster along with all Confluent Platform components in your Docker environment.
Now i change to a Linux-Virtual-Maschine with IP: 192.168.94.130Ĭheck access to the Windows Topic: docker run -rm confluentinc/cp-kafka bash -c "kafka-topics -bootstrap-server 192.168.2.22:9092 -list" I downloaded docker-compose.yml from and started it in a cmd-console with docker-compose up -dĬreate Topic: docker exec kafka1 kafka-topics -bootstrap-server localhost:9092 -create -topic my-Windows-Topic-1Ĭheck access to Topic: in different ways (but in the same cmd-console) docker exec kafka1 kafka-topics -bootstrap-server localhost:9092 -listĭocker exec kafka1 kafka-topics -bootstrap-server localhost:19092 -listĭocker exec kafka1 kafka-topics -bootstrap-server localhost:29092 -listĭocker exec kafka1 kafka-topics -bootstrap-server 192.168.2.22:9092 -listĭocker exec kafka1 kafka-topics -bootstrap-server 192.168.2.22:29092 -listĭocker run -rm confluentinc/cp-kafka bash -c "kafka-topics -bootstrap-server 192.168.2.22:9092 -list"ĭocker run -rm confluentinc/cp-kafka bash -c "kafka-topics -bootstrap-server 192.168.2.22:29092 -list"Īll the above commands show the same output so far On my Windows maschine with the IP-Address: 192.168.2.22 How connect two kafka clusters on different VM's together ?
0 kommentar(er)
