Page History

...

Note that a higher / lower configured timeout doesn't change how long requests actually run in the herder - currently, if a request exceeds the default timeout of 90 seconds we simply return with the a 500 Internal Server Error response but the request isn't interrupted or cancelled and is allowed to continue to completion. Furthermore, Another thing to note is that each connector config validation is anyway is  done on its own thread via a cached thread pool executor in the herder (create / update connector requests are processed asynchronously by simply writing a record to the Connect cluster's config topic, so config validations are the only relevant operation here).

...