Skip to content

[Bug]: ElasticsearchIO should use RetryPolicy in case of connectivity issues #30036

@bvolpato

Description

@bvolpato

What happened?

ElasticsearchIO has proper handling for 429 Too Many Requests, but high load to Elasticsearch may be expressed through several other symptoms.

For example, I've noticed Connection reset and Broken pipe. Failing the bundle may impact the pipeline negatively, when the intent of the user is just to try the Elasticsearch operation.

It would be great to revisit the default RetryPredicate to also retry in those connectivity issues.

Issue Priority

Priority: 3 (minor)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions