Shawn Heisey created SOLR-6717:
----------------------------------
Summary: Indexing performance when sending updates to incorrect
core is terrible
Key: SOLR-6717
URL: https://issues.apache.org/jira/browse/SOLR-6717
Project: Solr
Issue Type: Bug
Components: SolrCloud
Affects Versions: 4.10.2
Reporter: Shawn Heisey
Fix For: 5.0, Trunk
A user on the mailing list was sending document updates to a random node/core
in his SolrCloud. Performance was not scaling anywhere close to what was
expected. Basically, indexing performance was not scaling when adding shards
and servers.
As soon as the user implemented a smart router that was aware of the cloud
structure and could send to the proper shard leader, performance scaled exactly
as expected. It's not Java code, so CloudSolrServer was not an option.
There will always be some overhead involved when sending update requests to the
wrong shard replica, but hopefully something can be done about the performance
hit.
(I will include a link to the apache mail archives as soon as the summary
message becomes available).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
