[
https://issues.apache.org/jira/browse/SOLR-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670091#comment-13670091
]
Shawn Heisey edited comment on SOLR-4878 at 5/30/13 6:11 AM:
-------------------------------------------------------------
One workaround is this:
{noformat}
<infoStream file="INFOSTREAM-${solr.core.name}.txt">false</infoStream>
{noformat}
I've initially filed the issue as a bug, but I'm not entirely sure that's
correct.
was (Author: elyograg):
One workaround is this:
<infoStream file="INFOSTREAM-${solr.core.name}.txt">false</infoStream>
I've initially filed the issue as a bug, but I'm not entirely sure that's
correct.
> Change default directory for infostream from CWD to dataDir
> -----------------------------------------------------------
>
> Key: SOLR-4878
> URL: https://issues.apache.org/jira/browse/SOLR-4878
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.3
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Fix For: 5.0, 4.4
>
>
> The default directory for the infoStream file is CWD. In a multicore system
> where all the cores share similar configs, the output from all cores is
> likely to end up in the same file. Although this is sometimes the desired
> outcome, it seems less than ideal. If you've got cores that literally share
> the same config file, or you're using SolrCloud where more than one core on
> the system uses the same config set, you won't have the option of putting
> different files in different configs.
> If the default directory were dataDir rather than CWD, each core would get
> its own infostream file. You could still get the original behavior by
> specifying an absolute path.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]