What causes a "Remote connection timed out because no metadata was received" error for pipelines?
ERROR_MESSAGE: Remote connection timed out because no metadata was received from the source in `pipelines_extractor_get_offsets_timeout_ms` (20000 ms). Check your pipeline configuration. No stderr returned.
Error Code is
Subprocess timed out is documented in our doc site as it is a common error with S3 Pipelines click here to learn about it.
This error occurs when there are connectivity issues between a SingleStore DB node and the data source (e.g. Kafka cluster or S3). This error is particularly common when using S3 pipelines because of throttling and other S3 behavior.
To solve this issue, edit the value of
pipelines_extractor_get_offsets_timeout_ms. Increase this value to eliminate the timeout error.
check with AWS on the S3 side whether there is any intermittent connectivity issue with the S3 bucket.
Click here to learn more about how to handle Pipeline Errors.