[
https://issues.apache.org/jira/browse/SOLR-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13895687#comment-13895687
]
Jesse Sipprell commented on SOLR-5704:
--------------------------------------
The {{solr.xml}} I posted was initially just copy-and-pasted from some site
that documented it (which also suggested that these values not be altered). The
only values we have changed are {{coreRootDirectory}}, {{host}}, {{zkHost}} and
(I think) {{zkClientTimeout}}.
We don't use transient cores so the value isn't terribly relevant to us. In
fact, we use configuration management systems to manage core directories and
core.properties files in a totally different location separate from
{{solr.home}} and {{solr.xml}}. The only reason this (the problem discussed in
this ticket) is an issue for us is because it makes it impossible to perform
dynamic shardsplitting as the user we run Solr as doesn't have write access to
{{solr.home}}.
Thanks,
Jesse
> solr.xml coreNodeDirectory is ignored when creating new cores via REST(ish)
> apis
> --------------------------------------------------------------------------------
>
> Key: SOLR-5704
> URL: https://issues.apache.org/jira/browse/SOLR-5704
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.6.1
> Environment: x86_64 Linux
> x86_64 Sun Java 7_u21
> Reporter: Jesse Sipprell
> Assignee: Alan Woodward
> Priority: Minor
> Labels: solr.xml
>
> "New style" core.properties auto-configuration works correctly at startup
> when {{$\{coreRootDirectory\}}} is specified in {{$\{solr.home\}/solr.xml}},
> however it does not work if a core is later created dynamically via either
> (indirectly) the collection API or (directly) the core API.
> Core creation is always attempted in {{$\{solr.home\}}}.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
