On 1/10/2018 8:33 AM, Bernd Fehling wrote:
after some strange search results I was trying to locate the problem
and it turned out that it starts with bulk loading with SolrJ
and ConcurrentUpdateSolrClient.Builder with several threads.
I assume that ConcurrentUpdateSolrClient.Builder is _NOT_ thread safe
according the docs send to the indexer?
Why would you need the Builder to be threadsafe?
The actual client object (ConcurrentUpdateSolrClient) should be
perfectly threadsafe, but the Builder probably isn't, and I can't think
of any reason to try and use it with multiple threads. In a
well-constructed program, you will use the Builder exactly once, in an
initialization thread, and then have all the indexing threads use the
client object that the Builder creates.
I hope you're aware that the concurrent client swallows all indexing
errors and does not tell your program about them.
Thanks,
Shawn
