falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepak Barr (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FALCON-1756) Remove PID files on service stop
Date Mon, 18 Jan 2016 18:13:39 GMT
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

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

View raw message