ryerraguntla opened a new pull request, #3729: URL: https://github.com/apache/iggy/pull/3729
# Pull request draft For issue: https://github.com/apache/iggy/issues/3728 Create the PR from branch `fix/elasticsearch-sink-test-flakiness` against `apache/iggy` `master` (or `main` if that is the default). Copy **Title** and **Body** below into the PR form. Do **not** include `cve-issue-drafts/` in the PR. --- ## Title fix(connectors): harden Elasticsearch sink test readiness --- ## Body ## Summary - Fixes flaky Elasticsearch sink integration test where `iggy-connectors` never becomes healthy because sink `open()` can hang on Elasticsearch HTTP with no client timeout, while the connectors HTTP API only binds after plugin open. - Hardens the Elasticsearch Testcontainers fixture: use `127.0.0.1`, always re-check `/_cluster/health` on reuse attach, self-heal a wedged `iggy-test-elasticsearch` container only, and sweep stale harness indices older than 30 minutes. - Improves harness readiness: poll connectors `/health` and fail fast if the child process dies during retries; refresh the index before document-count polls in the sink fixture. Closes #3728 ## Test plan - [ ] `cargo fmt --all` - [ ] `cargo sort --no-format --workspace` - [ ] `cargo clippy -p iggy_connector_elasticsearch_sink -p integration --all-features --all-targets -- -D warnings` - [ ] `cargo test -p integration -- connectors::elasticsearch::elasticsearch_sink::elasticsearch_sink_stores_json_messages` - [ ] Confirm `docker rm -f` recovery targets only `iggy-test-elasticsearch` (no other Elasticsearch containers) - [ ] Optional: leave a reused `iggy-test-elasticsearch` running and re-run the sink test to verify reuse + readiness path ## Notes - Container force-remove uses the fixed harness name `iggy-test-elasticsearch` only. - Stale index sweep is best-effort and age-gated so concurrent harness tests sharing the reused container are not disrupted. -- 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]
