You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:08:27 UTC
[jira] [Updated] (BEAM-5988) ElasticsearchIO listener timeout
[ https://issues.apache.org/jira/browse/BEAM-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Beam JIRA Bot updated BEAM-5988:
--------------------------------
Labels: stale-P2 (was: )
> 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: P2
> Labels: stale-P2
>
> 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)