krishvishal opened a new issue, #3078:
URL: https://github.com/apache/iggy/issues/3078
All Elasticsearch integration tests are timing-out after 120 seconds in CI:
- `elasticsearch_source_produces_bulk_messages`
- `elasticsearch_source_produces_messages_to_iggy`
- `state_persists_across_connector_restart`
- `elasticsearch_sink_handles_bulk_messages`
- `elasticsearch_sink_preserves_json_structure`
- `elasticsearch_sink_stores_json_messages`
- `elasticsearch_source_handles_empty_index`
The root cause is the same as #3077 (Iceberg): the Elasticsearch container
uses WaitFor::message_on_stdout("started") to detect readiness, which is
unreliable because:
1. The word "started" appears in an early log line ("deprecation component
started") before the HTTP API is ready
2. Log-based detection is generally unreliable in CI due to buffering and
timing issues
Additionally, both sink and source fixtures have redundant 15-second health
check polling loops (30 attempts × 500ms) that run after container startup, and
the source tests have unnecessarily long sleep durations.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
