[ https://issues.apache.org/jira/browse/BEAM-3848?focusedWorklogId=88203&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-88203 ]
ASF GitHub Bot logged work on BEAM-3848: ---------------------------------------- Author: ASF GitHub Bot Created on: 05/Apr/18 19:24 Start Date: 05/Apr/18 19:24 Worklog Time Spent: 10m Work Description: timrobertson100 commented on issue #4905: [BEAM-3848] Enables ability to retry Solr writes on error (SolrIO) URL: https://github.com/apache/beam/pull/4905#issuecomment-379049114 @iemejia - that should be rebased, squashed and presented as one commit. Please grab me on slack if you see otherwise and I'll address it. I'm afraid that with a rebase to origin/master to include Romain's recent PRs did not fix the thread problem so the `testWriteRetry()` remains with the hack to await thread termination, and manual unregistering of `SolrZKClient` from threadleak detection. Perhaps we/Roman/I could diagnose and tackle that later? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 88203) Time Spent: 7h (was: 6h 50m) > SolrIO: Improve retrying mechanism in client writes > --------------------------------------------------- > > Key: BEAM-3848 > URL: https://issues.apache.org/jira/browse/BEAM-3848 > Project: Beam > Issue Type: Improvement > Components: io-java-solr > Affects Versions: 2.2.0, 2.3.0 > Reporter: Tim Robertson > Assignee: Tim Robertson > Priority: Minor > Time Spent: 7h > Remaining Estimate: 0h > > A busy SOLR server is prone to return RemoteSOLRException on writing which > currently failsĀ a complete task (e.g. a partition of a spark RDD being > written to SOLR). > A good addition would be the ability to provide a retrying mechanism for the > batch in flight, rather than failingĀ fast, which will most likely trigger a > much larger retry of more writes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)