[
https://issues.apache.org/jira/browse/SOLR-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998335#comment-13998335
]
Mark Miller commented on SOLR-6055:
-----------------------------------
The transaction log does have it's own dir as far as I remember - it just
defaults to being relative to the data dir I think.
Seems to me the likely right thing to do is simply throw an init exception when
the transaction log doesn't have it's own full path and an ephemeral directory
factory is used.
> TestMiniSolrCloudCluster has data dir in test's CWD
> ---------------------------------------------------
>
> Key: SOLR-6055
> URL: https://issues.apache.org/jira/browse/SOLR-6055
> Project: Solr
> Issue Type: Bug
> Reporter: Ryan Ernst
>
> While investigating one of the test failures created when tightening test
> permissions to restrict write access to CWD (see LUCENE-5650), I've found
> {{TestMiniSolrCloudCluster}} is attemping to write transaction logs to
> {{$CWD/data/tlog}}.
> I've traced this down to two things which are happening:
> # The test uses {{RAMDirectoryFactory}}, which always returns true for
> {{isAbsolute}}. This causes the directory factory to *not* adjust the
> default relative to bring it under the instance dir.
> # The {{UpdateLog}} creates its tlog file with the relative data dir.
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
