Wait a minute ... this fixVersion update caught my eye.
the 4.0-BETA release highlights said...
* Improved Solrj client performance with Solr Cloud: updates are
only sent to leaders by default.
...and i just merged that into the 4.0 final release highlights -- but
based on this issue description and fix version, i'm now wondering if that
was a mistake in the release announcement?
: Mark Miller updated SOLR-3154:
: ------------------------------
:
: Fix Version/s: 4.1
:
: > SolrJ CloudServer should be leader and network aware when adding docs
: > ---------------------------------------------------------------------
: >
: > Key: SOLR-3154
: > URL: https://issues.apache.org/jira/browse/SOLR-3154
: > Project: Solr
: > Issue Type: Improvement
: > Components: SolrCloud
: > Affects Versions: 4.0-ALPHA
: > Reporter: Grant Ingersoll
: > Assignee: Mark Miller
: > Priority: Minor
: > Fix For: 4.1, 5.0
: >
: > Attachments: SOLR-3154.patch
: >
: >
: > It would be good when indexing if the SolrJ CloudServer was leader aware so
that we could avoid doing an extra hop for the data. It would also be good if
one could easily set things up based on data locality principles. This might
mean that CloudServer is aware of where on the network it is and would pick
leaders that are as close as possible (i.e. local, perhaps.) This would come
in to play when working with tools like Hadoop or other grid computing
frameworks.
:
: --
: This message is automatically generated by JIRA.
: If you think it was sent incorrectly, please contact your JIRA administrators
: For more information on JIRA, see: http://www.atlassian.com/software/jira
:
: ---------------------------------------------------------------------
: To unsubscribe, e-mail: [email protected]
: For additional commands, e-mail: [email protected]
:
:
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
