You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Konstantine Karantasis (Jira)" <ji...@apache.org> on 2021/02/04 00:12:00 UTC

[jira] [Updated] (KAFKA-12259) Consolidated Status endpoint returns 500 when config provider can't find a config

     [ https://issues.apache.org/jira/browse/KAFKA-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantine Karantasis updated KAFKA-12259:
-------------------------------------------
    Summary: Consolidated Status endpoint returns 500 when config provider can't find a config  (was: Consolidated Status endpoint return 500 whe config provider can't find a config)

> Consolidated Status endpoint returns 500 when config provider can't find a config
> ---------------------------------------------------------------------------------
>
>                 Key: KAFKA-12259
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12259
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Magesh kumar Nandakumar
>            Priority: Major
>             Fix For: 2.8.0, 2.7.1, 2.6.2
>
>
> The consolidated connectors endpoint connectors?expand=status return a `500` error when any of the connector's has an exception from the config provider.  [https://github.com/apache/kafka/blob/e9edf104866822d9e6c3b637ffbf338767b5bf27/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/AbstractHerder.java#L287]
>  The status endpoint doesn't need the complete list of configs and just requires the Connector Class to infer if it's a `Source` or a `Sink`. The failed connector status should be returned as `Failed` instead of the endpoint returning a 500.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)