Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

When selectively stopping Connect, CLI also stops ksql-server and Confluent Control Center #70

Open
rmoff opened this issue Mar 14, 2018 · 0 comments

Comments

@rmoff
Copy link
Contributor

rmoff commented Mar 14, 2018

If I selectively shutdown Connect, CLI also stops ksql-server and Confluent Control Center.

Robin@asgard02 ~> confluent status
control-center is [UP]
ksql-server is [UP]
connect is [UP]
kafka-rest is [UP]
schema-registry is [UP]
kafka is [UP]
zookeeper is [UP]
Robin@asgard02 ~> confluent stop connect
Using CONFLUENT_CURRENT: /var/folders/q9/2tg_lt9j6nx29rvr5r5jn_bw0000gp/T/confluent.6yVWsyCf
Stopping control-center
control-center is [DOWN]
Stopping ksql-server
ksql-server is [DOWN]
Stopping connect
connect is [DOWN]
Robin@asgard02 ~> confluent status
control-center is [DOWN]
ksql-server is [DOWN]
connect is [DOWN]
kafka-rest is [UP]
schema-registry is [UP]
kafka is [UP]
zookeeper is [UP]

(If I selectively startup Connect, CLI does not change the state of ksql-server or Confluent Control Center)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant