[jira] [Issue Comment Deleted] (FALCON-1756) Remove PID files on service stop

["Deepak Barr (JIRA)" <ji...@apache.org>]

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

Deepak Barr updated FALCON-1756:
--------------------------------
    Comment: was deleted

(was: Sure, we can do that. Hadoop daemons do the same. Will update the patch.)

> Remove PID files on service stop
> --------------------------------
>
>                 Key: FALCON-1756
>                 URL: https://issues.apache.org/jira/browse/FALCON-1756
>             Project: Falcon
>          Issue Type: Improvement
>    Affects Versions: 0.9
>            Reporter: Deepak Barr
>            Assignee: Deepak Barr
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: FALCON-1756-v1.patch, FALCON-1756-v2.patch, FALCON-1756.patch
>
>
> Currently, 
> When someone runs falcon-stop, falcon.pid file is not removed. 
> So, if someone runs falcon-stop again, it will again try to kill the same PID and will get the following error -
> bin/service-stop.sh: line 37: kill: (985) - No such process
> Also, in rarest case, if the PID is subsequently assigned to some other process, the stop script might try to kill that process.
> It is generally a good practice to remove the PID file after the process is stopped.
> Evidently, similar thing happens with prism-stop as well.
> Thoughts ??



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)