Description
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).
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 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.
Attachments
Issue Links
- links to