[
https://issues.apache.org/jira/browse/SOLR-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506444#comment-13506444
]
Per Steffensen edited comment on SOLR-4120 at 11/29/12 4:16 PM:
----------------------------------------------------------------
h4. SOLR-4120.patch
h5. Where does it fit
* It fits on top of revision 1412602 of branch lucene_solr_4_0, where the patch
for SOLR-4114 has already been applied. The following should work if you have a
checkout of revision 1412602 of branch lucene_solr_4_0
** cd <checkout-folder>
** patch -s -p0 < SOLR-4114.patch
** patch --ignore-whitespace -p0 < SOLR-4120.patch
You need the --ignore-whitespace - at least with my version of patch on Show
Leopard. Probably because I do not have the correct Solr code-style installed
in my Eclipse. Hmmm, probably should do that.
h5. Content of the patch
The patch modifies the create operation of the Solr Collection API, so that it
allows to provide a list of Solrs that the shards for the new collection should
be spread across
* Param key: createNodeSet (OverseerCollectionProcessor.CREATE_NODE_SET)
* Param value: comma-separated list of node-names (equal to the node-names
received from ClusterState.getLiveNodes())
* Param is not mandatory. If not provided the created collection will still
have its shards spread across all live nodes
h5. Testing
BasicDistributedZkTest.testCollectionAPI has been modified to also test this
feature
was (Author: steff1193):
h4. SOLR-4120.patch
h5. Where does it fit
* It fits on top of revision 1412602 of branch lucene_solr_4_0, where the patch
for SOLR-4114 has already been applied. The following should work if you have a
checkout of revision 1412602 of branch lucene_solr_4_0
** cd <checkout-folder>
** patch -s -p0 < SOLR-4114.patch
** patch --ignore-whitespace -p0 < SOLR-4120.patch
You need the --ignore-whitespace - at least with my version of patch on Show
Leopard. Probably because I do not have the correct Solr code-style installed
in my Eclipse. Hmmm, probably should do that.
h5. Content of the patch
The patch modifies the create operation of the Solr Collection API, so that i
allows to provide a list of Solrs that the shards for the new collection should
be spread across
* Param key: createNodeSet (OverseerCollectionProcessor.CREATE_NODE_SET)
* Param value: comma-separated list of node-names (equal to the node-names
received from ClusterState.getLiveNodes())
* Param is not mandatory. If not provided the created collection will still
have its shards spread across all live nodes
h5. Testing
BasicDistributedZkTest.testCollectionAPI has been modified to also test this
feature
> Collection API: Support for specifying a list of solrs to spread a new
> collection across
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-4120
> URL: https://issues.apache.org/jira/browse/SOLR-4120
> Project: Solr
> Issue Type: New Feature
> Components: multicore, SolrCloud
> Affects Versions: 4.0
> Reporter: Per Steffensen
> Assignee: Per Steffensen
> Priority: Minor
> Labels: collection-api, multicore, shard, shard-allocation
> Attachments: SOLR-4120.patch
>
>
> When creating a new collection through the Collection API, the Overseer
> (handling the creation) will spread shards for this new collection across all
> live nodes.
> Sometimes you dont want a collection spread across all available nodes. Allow
> for the create operation of the Collection API, to take a createNodeSet
> parameter containing a list of Solr to spread the new shards across. If not
> provided it will just spread across all available nodes (default).
> For an example of a concrete case of usage see:
> https://issues.apache.org/jira/browse/SOLR-4114?focusedCommentId=13505506&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13505506
--
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]
