[ https://issues.apache.org/jira/browse/SOLR-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Potter reassigned SOLR-6946: ------------------------------------ Assignee: Timothy Potter > create_core should accept the port as an optional param > ------------------------------------------------------- > > Key: SOLR-6946 > URL: https://issues.apache.org/jira/browse/SOLR-6946 > Project: Solr > Issue Type: Bug > Affects Versions: 5.0 > Reporter: Anshum Gupta > Assignee: Timothy Potter > Priority: Critical > > While documenting legacy distributed search, for the purpose of an example, I > wanted to start 2 instances on the same machine in standalone mode with a > core each and the same config set. > Here's what I did to start the 2 nodes: > {code} > bin/solr start -s example/nodes/node1 -p 8983 > bin/solr start -s example/nodes/node2 -p 8984 > {code} > So far so good. Now, create_core doesn't accept a port number and so it > pseudo-randomly picks a node to create the core i.e. I can't create a core > using scripts on both nodes smoothly unless we support "-p <port number>" > with that call (and may be collection too?). > FYI, I also tried : > {code} > bin/solr start -s example/nodes/node1 -p 8983 -e techproducts > bin/solr start -s example/nodes/node2 -p 8984 -e techproducts > {code} > but this failed as -e overrides -s. I don't really remember why we did that, > but perhaps we can consider not overriding -s, even when -e is specified i.e. > copy whatever is required and use -s. -- 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