[ 
https://issues.apache.org/jira/browse/SOLR-16254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880959#comment-17880959
 ] 

ASF subversion and git services commented on SOLR-16254:
--------------------------------------------------------

Commit 14c9575611e2c77c713760a9d01c5f8cb88cad23 in solr's branch 
refs/heads/main from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=14c9575611e ]

SOLR-16254: Clarify when a create needs to be run on the same server as Solr. 
(#2698)

* Introduce new header for help text to clarify when you must run on the same 
server as solr.

* small formatting tweak to improve whitespace in cli output

* use similar text for similar meaning

> solr standalone: in-correct information in the help message for "bin/solr 
> create_core"
> --------------------------------------------------------------------------------------
>
>                 Key: SOLR-16254
>                 URL: https://issues.apache.org/jira/browse/SOLR-16254
>             Project: Solr
>          Issue Type: Bug
>          Components: cli
>    Affects Versions: 9.0
>            Reporter: Sun Rui
>            Assignee: Eric Pugh
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> There is a statement in the help message for "bin/solr create_core":
> _*When a configSet is used, this can be run from remote (non-Solr) hosts.  If 
> pointing at a non-configSet directory, this must be run from the host that 
> you wish to create the core on.*_
> However, this is not case.
> Suppose there is a solr server instance launched at 192.168.0.100:8983. On a 
> different host (non-solr host), use the following command to create a new 
> core:
> SOLR_HOST=192.168.0.100 bin/solr create_core -c test -d _default -p 8983
> an error message is output like the following:
> ERROR: Error CREATEing SolrCore 'test': Unable to create core [test] Caused 
> by: Can't find resource 'solrconfig.xml' in classpath or '/var/solr/data/test'
> check the core status:
> $ curl [http://192.168.0.100:8983/solr/admin/cores]
> {
>   "responseHeader":
> {     "status":0,     "QTime":0}
> ,
>   
> "initFailures":\{"test":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
>  Could not load conf for core test: Error loading solr config from 
> /opt/solr-9.0.0/server/solr/test/conf/solrconfig.xml"},
>   "status":{}}
> You can see that the core was created but can't be loaded by the solr server 
> (because of no configuration files can be found in the conf sub-directory of 
> the instance directory).
> As a comparison, we can remotely create a new core using the following Solr 
> API:
> curl 
> "http://192.168.0.100:8983/solr/admin/cores?action=CREATE&name=test&instanceDir=test&configSet=_default";
>  
> My question is how to fix this issue. Do we want to fixup the statement to 
> match the real behavior or update the create_core tool to support remotely 
> creating a core ?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to