Chris Egerton created KAFKA-15563:
-------------------------------------
Summary: Provide informative error messages when Connect REST
requests time out
Key: KAFKA-15563
URL: https://issues.apache.org/jira/browse/KAFKA-15563
Project: Kafka
Issue Type: Improvement
Components: KafkaConnect
Reporter: Chris Egerton
Assignee: Chris Egerton
The Kafka Connect REST API has a hardcoded timeout of 90 seconds. If any
operations take longer than that, a 500 error response is returned with the
message "Request timed out" (see
[here|https://github.com/apache/kafka/blob/7e1c453af9533aba8c19da2d08ce6595c1441fc0/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/rest/HerderRequestHandler.java#L70]).
This can be a source of frustration for users, who want to understand what is
causing the request to time out. This can be specific to the request (for
example, a connector's [custom multi-property validation
logic|https://kafka.apache.org/35/javadoc/org/apache/kafka/connect/connector/Connector.html#validate(java.util.Map)]
is taking too long), or applicable to any request that goes through the
herder's tick thread (for which there are a variety of possible causes).
We can give users better, immediate insight into what is causing requests to
time out by including information about the last possibly-blocking operation
the worker performed while servicing the request (or attempting to enter a
state where all preconditions necessary to service the request have been
satisfied), and when the worker began that operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
