lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank Wesemann (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1905) Multicore admin/cores?action=CREATE
Date Fri, 10 Sep 2010 12:15:33 GMT

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

Frank Wesemann commented on SOLR-1905:
--------------------------------------

If solrconfig.xml specifies a dataDir the dataDir parameter to the CREATE action is ignored.
This is due to the fact that in the SolrCore Construktor the configfile takes precedence over
the CoreDescriptor.
Shouldn't the CoreDescriptor take precedence?

> Multicore admin/cores?action=CREATE 
> ------------------------------------
>
>                 Key: SOLR-1905
>                 URL: https://issues.apache.org/jira/browse/SOLR-1905
>             Project: Solr
>          Issue Type: Bug
>          Components: multicore
>    Affects Versions: 1.4
>         Environment: Solaris x86, jdk 1.6, tomcat 2.0.16
>            Reporter: Robbin Turner
>
> Using the information off the CoreAdmin Wiki,  I initially set up Solr with one core
with solr.xml looking like the following:
> <solr persistent="true" sharedLib="lib">
>                 <cores adminPath="/admin/cores" sharedSchema="false">
>                                 <core name="core1" instanceDir="/opt/solrcores"
>                                                 dataDir="/data1/core1"
>                                                 config="solrconfig.xml"
>                                                 properties="conf/solrcore-core1.properties"
>                                                 schema="schema-core1.xml" />
>                 </cores>
> </solr>
> The application starts up fine and I can get to the http://<solrhost:port>/solrcores.
 I see the link for Admin core1 and everything is running fine.  I then enter the URL:
> http://<solrhost:port>/solrcores/admin/cores?action=CREATE&name=core2&instanceDir=/opt/solrcores&config=solrconfig-core2.xml&schema=schema-core2.xml&dataDir=/data1/core2&properties=conf/solrcore-core2.properties
> to create my next core, core2.  The new core is registered and does show in the base
URL, http://<solrhost:port>/solrcores, which now list links for Admin core1 and Admin
core2.
> When I looked in the solr.xml, I see the following:
> <solr persistent="true" sharedLib="lib">
>                 <cores adminPath="/admin/cores" sharedSchema="false">
>                                 <core name="core1" instanceDir="/opt/solrcores" schema="schema-core1.xml"
properties="conf/solrcore-core1.properties" dataDir="/data1/core1" />
>                                 <core name="core2" instanceDir="/opt/solrcores" schema="schema-core2.xml"
dataDir="/data1/core2"  />
>                 </cores>
> </solr>
> Shouldn't all the parameters be added to the solr.xml core2 that were passed in from
the URL?  And why did the config="solrconfig.xml" get removed from the core1 definition?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message