Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ksqlDB should indicate if no connector tasks are running #4321

Closed
rmoff opened this issue Jan 15, 2020 · 1 comment · Fixed by #4323
Closed

ksqlDB should indicate if no connector tasks are running #4321

rmoff opened this issue Jan 15, 2020 · 1 comment · Fixed by #4323

Comments

@rmoff
Copy link
Contributor

rmoff commented Jan 15, 2020

ksql> show connectors;

 Connector Name | Type | Class                                       | Status
---------------------------------------------------------------------------------------------------
 SINK_INFLUX_03 | SINK | io.confluent.influxdb.InfluxDBSinkConnector | RUNNING (1/1 tasks RUNNING)
 SINK_INFLUX_04 | SINK | io.confluent.influxdb.InfluxDBSinkConnector | RUNNING (0/1 tasks RUNNING)

IMO the SINK_INFLUX_04 connector should show something to indicate that there might be a problem, e.g.

ksql> show connectors;

 Connector Name | Type | Class                                       | Status
---------------------------------------------------------------------------------------------------
 SINK_INFLUX_03 | SINK | io.confluent.influxdb.InfluxDBSinkConnector | RUNNING (1/1 tasks RUNNING)
 SINK_INFLUX_04 | SINK | io.confluent.influxdb.InfluxDBSinkConnector | WARNING (0/1 tasks RUNNING)

WDYT @agavra ?

@ybyzek
Copy link
Contributor

ybyzek commented Jan 15, 2020

Just to differentiate related issues:

  1. It should highlight there is a problem with the connector/task
  2. It should surface the exact error or reason why the connect worker failed --> Surface errors from Connect workers #3775
  3. It should surface the exact error or reason why the connector/task failed --> should this be separate from Surface errors from Connect workers #3775 ?

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

Successfully merging a pull request may close this issue.

2 participants