You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Deepak Barr (JIRA)" <ji...@apache.org> on 2016/01/18 19:13:39 UTC

[jira] [Created] (FALCON-1756) Remove PID files on service stop

Deepak Barr created FALCON-1756:
-----------------------------------

             Summary: Remove PID files on service stop
                 Key: FALCON-1756
                 URL: https://issues.apache.org/jira/browse/FALCON-1756
             Project: Falcon
          Issue Type: Improvement
            Reporter: Deepak Barr
            Assignee: Deepak Barr
            Priority: Minor


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)