[jira] [Updated] (BIGTOP-945) Service lock files need to match init script name

["Sean Mackrory (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BIGTOP-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Mackrory updated BIGTOP-945:
---------------------------------

    Attachment: 0001-BIGTOP-945.-Service-lock-files-need-to-match-init-sc.patch

Here's a better patch. It's consistent for all the services, and works for all the ones I tested (so far, HBase, Hive, Sqoop, HDFS).
                
> Service lock files need to match init script name
> -------------------------------------------------
>
>                 Key: BIGTOP-945
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-945
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Critical
>             Fix For: 0.6.0
>
>         Attachments: 0001-BIGTOP-945.-Service-lock-files-need-to-match-init-sc.patch, 0001-BIGTOP-945.-Service-lock-files-need-to-match-init-sc.patch
>
>
> The base name of the lock file created by init scripts needs to base name of the init script itself, because services are only shutdown if their lock file is present. Currently the Hadoop services do not have matching init scripts and lock files.
> This is not a problem in the recent patches to move Sqoop, Hive and HBase to similar templates, but it shouldn't be overridable in the .svc files. The template should enforce any system-specific LOCKDIR locations and ensure the outputted init script has the same name as the lockfile.

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