[
https://issues.apache.org/jira/browse/SOLR-6421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169359#comment-14169359
]
Ralph Tice edited comment on SOLR-6421 at 10/13/14 2:51 PM:
------------------------------------------------------------
Nevermind, I see the docs don't even mention createNodeSet anymore. :)
was (Author: ralph.tice):
Could we at least address the usability issue here, and if port_solr is passed
into createNodeSet throw a validation error that suggests node parameter
instead?
> ADDREPLICA doesn't respect :port_solr designation
> -------------------------------------------------
>
> Key: SOLR-6421
> URL: https://issues.apache.org/jira/browse/SOLR-6421
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.10
> Environment: Ubuntu 14.04
> Reporter: Ralph Tice
> Labels: SolrCloud, difficulty-easy, impact-medium
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> When I issue an ADDREPLICA call like so:
>
> http://localhost:8983/solr/admin/collections?action=ADDREPLICA&shard=myshard&collection=mycollection&createNodeSet=solr18.mycorp.com:8983_solr
> SolrCloud does not seem to respect the 8983_solr designation in the
> createNodeSet parameter and instead places the shard on any JVM on the
> machine instance. First attempt I got a replica on 8994_solr and second
> attempt to place a replica on 8983 got a replica on 8992_solr instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
