search

confluentinc / confluent-cli

Confluent Platform CLI
Other
60 stars 38 forks source link

CLI doesnt seem to be releasing everything #57

Open IDispose opened 6 years ago

IDispose commented 6 years ago

Confluent CP 4.0 installed on CentoOS 7.2 After installation started confluent start schema-reigstry

Played with producers and consumers

confluent stop confluent destroy

Tried restarting

confluent schema-registry

Got, Error starting zookeeper

confluent log zookeeper indicates that java coundnt bind to port 2181 because it's already in use.

Had to kill the 2 java processes holding on to 2181 and 9092.

kkonstantine commented 6 years ago

Were the processes that you had to explicitly kill long running? Or they just ran for a short period of time? From the ports these processes corresponded to zookeeper and kafka. A certain CLI instance controls only the processes that manages itself.

To troubleshoot more, try next time running confluent current to access the directory where CLI stores all its descriptors. If the metadata there do not match the running instances CLI won't be able to stop the running processes.