Shawn Heisey commented on SOLR-7826:

bq. The question is if we should discourage and warn about starting solr as 
root as well, since this is not recommended?

I would say yes to this.  I'd even go a little bit further.  The script should 
refuse to run (without the force option) any command that creates or modifies 
filesystem data -- but only if Solr also writes to the same filesystem 
location.  This would mean that creating collections in cloud mode and options 
like upconfig and downconfig would be perfectly acceptable to run as root.

> Permission issues when creating cores with bin/solr
> ---------------------------------------------------
>                 Key: SOLR-7826
>                 URL: https://issues.apache.org/jira/browse/SOLR-7826
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Shawn Heisey
>            Assignee: Jan H√łydahl
>            Priority: Minor
>              Labels: newdev
>             Fix For: 6.3, master (7.0)
>         Attachments: SOLR-7826.patch, SOLR-7826.patch
> Ran into an interesting situation on IRC today.
> Solr has been installed as a service using the shell script 
> install_solr_service.sh ... so it is running as an unprivileged user.
> User is running "bin/solr create" as root.  This causes permission problems, 
> because the script creates the core's instanceDir with root ownership, then 
> when Solr is instructed to actually create the core, it cannot create the 
> dataDir.
> Enhancement idea:  When the install script is used, leave breadcrumbs 
> somewhere so that the "create core" section of the main script can find it 
> and su to the user specified during install.

This message was sent by Atlassian JIRA

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

Reply via email to