I have issue while running kafka in wsl in a windows 10 machine.
When I use “confluent local services start”, it will keep showing the “Starting Zookeeper” but if I open another wsl window and try “confluent local services status”, it shows the Zookeeper is up. See the attached screenshot.
If I run “confluent local services start” again, it knows Zookeeper has been started and stuck in the next process; “Starting Kafka”. Again, if I check the status, Kafka is already up. I need to keep do this one by one until all have been started.
Any idea? I assume the “start” command use the same logic as in “status” to check the process but how come “start” does not know it is up but “status” knows it correctly?