[jboss-jira] [JBoss JIRA] (WFLY-89) Spurious server dirs created when directory-grouping="by-type" is set

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796875#comment-12796875 ] 

Brian Stansberry edited comment on WFLY-89 at 8/14/13 5:09 PM:
---------------------------------------------------------------

I think your point about creating the directories is solid. But I have doubts about using $JBOSS_HOME/domain/servers/<server-name> when directory-grouping="by-type". Perhaps $JBOSS_HOME/domain/data/servers/<server-name> or $JBOSS_HOME/domain/tmp/servers/<server-name>. Use the existing writable areas associated with the HC process.  The point of the whole by-type thing was to get all file writing into locations that map into the File Hierarchy Standard for Unix systems, particularly with RPM-based distributions of the server. The domain/data and domain/tmp dirs should already be set up for that. So we should make sure this file fits in as well.

I recommend you discuss this with Fernando Nasser and pick the appropriate location based on the expected semantics for the data we'll be storing in these dirs. Alternatives:

1) Since we have no idea what some upstream code might be writing here, assume it's meant to survive system and process restart. Put it in domain/data.

2) We don't expect anyone to actually write anything here, and if they do they are wrong and should use jboss.server.data.dir, jboss.server.tmp.dir or jboss.server.log.dir. So treat this like all other tmp files that may not survive system or process restart. Put it in domain/tmp.

3) Something else you guys come up with that fits in with what we are doing for FHS compliance.

I'm ok with any of these.
                
      was (Author: brian.stansberry):
    I think your point about creating the directories is solid. But I have doubts about using $JBOSS_HOME/domain/servers/<server-name> when directory-grouping="by-type". Perhaps $JBOSS_HOME/domain/data/servers/<server-name> or $JBOSS_HOME/domain/tmp/servers/<server-name>. Use the existing writable areas associated with the HC process.  The point of the whole by-type thing was to get all file writing into locations that map into the File Hierarchy Standard for Unix systems, particularly with RPM-based distributions of the server. The domain/data and domain/tmp dirs should already be set up for that. So we should make sure this file fits in as well.

I recommend you discuss this with Fernando Nasser and pick the appropriate location based on the expected semantics for the data we'll be storing in these dirs. Alternatives:

1) Since we have no idea what some upstream code might be writing here, assuming its meant to survive system and process restart. Put it in domain/data.

2) We don't expect anyone to actually write anything here, and if they do they are wrong and should use the jboss.server.data.dir. So treat this like all other tmp files that may not survive system or process restart. Put it in domain/tmp.

3) Something else you guys come up with that fits in with what we are doing for FHS compliance.

I'm ok with any of these.
                  
> Spurious server dirs created when directory-grouping="by-type" is set
> ---------------------------------------------------------------------
>
>                 Key: WFLY-89
>                 URL: https://issues.jboss.org/browse/WFLY-89
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: James Perkins
>            Priority: Minor
>             Fix For: 8.0.0.Beta1
>
>
> Add directory-grouping="by-type" to the <host><servers> element in the stock host.xml and run domain.sh. The following empty directories are created:
> $JBOSS_HOME/domain/servers/server-one
> $JBOSS_HOME/domain/servers/server-two
> The content that would normally be in those dirs if directory-grouping="by-type" wasn't set appears to all be going where it should (e.g. under domain/data, domain/log etc) so the only issue here is the empty directories.

--
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