You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.
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)
The text was updated successfully, but these errors were encountered:
If I selectively shutdown Connect, CLI also stops ksql-server and Confluent Control Center.
(If I selectively startup Connect, CLI does not change the state of ksql-server or Confluent Control Center)
The text was updated successfully, but these errors were encountered: