You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2014/02/07 23:55:19 UTC

[jira] [Commented] (BIGTOP-1158) Solr "work" symlink creates infinite loop if you try to recurse through the directories

    [ https://issues.apache.org/jira/browse/BIGTOP-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13895191#comment-13895191 ] 

Sean Mackrory commented on BIGTOP-1158:
---------------------------------------

This patch actually causes the work symlink to get created inside the new deployment. One more reason it made sense to move CATALINA_BASE to /var/lib/.../ - it contains state data as well.

> Solr "work" symlink creates infinite loop if you try to recurse through the directories
> ---------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-1158
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1158
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Blocker
>         Attachments: 0001-BIGTOP-1158.-Solr-work-symlink-creates-infinite-loop.patch
>
>
> Solr's Tomcat deployment includes a symlink "work" that exists for the purpose of allow Tomcat to create some files to store state at run-time. The symlink previously point to /var/lib/solr, but with the Tomcat deployment now in /var/lib/solr/tomcat-deployment, if Tomcat tries to recurse and fully map the directory, it ended up in an infinite loop.
> Either the symlink doesn't need to exist at all (it seems Tomcat just creates the directory when it needs it, which it will redo if the Tomcat web application gets redeployed) or it needs to point to a peer of tomcat-deployment, like /var/lib/solr/work.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)