[
https://issues.apache.org/jira/browse/BEAM-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187651#comment-17187651
]
Yu Watanabe commented on BEAM-5988:
-----------------------------------
As far as referring to release-2.24.0 , retry mechanism seems to be implemented.
[https://github.com/apache/beam/blob/release-2.24.0/sdks/java/io/elasticsearch/src/main/java/org/apache/beam/sdk/io/elasticsearch/ElasticsearchIO.java#L1404]
> ElasticsearchIO listener timeout
> --------------------------------
>
> Key: BEAM-5988
> URL: https://issues.apache.org/jira/browse/BEAM-5988
> Project: Beam
> Issue Type: Bug
> Components: io-java-elasticsearch
> Reporter: Wout Scheepers
> Priority: P3
>
> Still getting a listener timeout when trying to insert a large amount of
> documents.
> ```
> java.io.IOException: listener timeout after waiting for [30000] ms
> at
> org.elasticsearch.client.RestClient$SyncResponseListener.get(RestClient.java:660)
> at org.elasticsearch.client.RestClient.performRequest(RestClient.java:219)
> at org.elasticsearch.client.RestClient.performRequest(RestClient.java:191)
> at
> org.apache.beam.sdk.io.elasticsearch.ElasticsearchIO$Write$WriteFn.flushBatch(ElasticsearchIO.java:1226)
> at
> org.apache.beam.sdk.io.elasticsearch.ElasticsearchIO$Write$WriteFn.finishBundle(ElasticsearchIO.java:1200)
> ```
> The listener timeouts are not handled in the underlying ES RestClient.
> A possible solution would be to catch these exceptions and include them in
> the retry handling mechanism
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
