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

Sean Mackrory commented on BIGTOP-945:
--------------------------------------

>> how removing LOCKDIR="/var/lock/subsys" from Sqoop, Hive and HBase would 
>> work?

Since all services should have a matching service name and lock file, the 
template will just re-use the service name for the lockfile no .svc file should 
be trying to override it.

>> why the asymmetric patch for all the hadoop daemons?

I remember thinking there was a reason not to do the same in the hadoop 
template, but not only do I not recall what it was, it just dawned on me that 
the shared template is going to be overwriting Hadoop's template anyway, so 
they might as well be using it the same way. Will update the patch (and if I 
remember the reason, I'll update the comment :) ) and re-test...
                
> 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
>
>
> 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

Reply via email to