accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-925) Launch scripts should use a PIDfile
Date Thu, 19 May 2016 19:18:12 GMT

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

Josh Elser commented on ACCUMULO-925:
-------------------------------------

bq. Is there a reason why we can't apply this back to 1.6?

Should probably have a discussion about it -- need to consider the impact on user automation
around our scripts. We haven't really identified how the scripts should be covered by our
compatibility statement (we have nothing about them now which is probably negligence). My
gut reaction is that it wouldn't be worth it, but I'm not against someone doing the work to
backport it (as long as we're sure we don't break scripts).

It also would require the .out/.err file rotation (or at least splitting that logic out).
IIRC, the hope was that usage of the existing start/stop-server and start/stop-all scripts
didn't change, but I don't remember enough to say it is definitely compatible.

> Launch scripts should use a PIDfile
> -----------------------------------
>
>                 Key: ACCUMULO-925
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-925
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: scripts
>            Reporter: Christopher Tubbs
>            Assignee: Billie Rinaldi
>             Fix For: 1.8.0
>
>         Attachments: ACCUMULO-925.1.patch, ACCUMULO-925.2.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Start scripts should create PIDfiles to store the PID of running processes in a well
known location (example: /var/run/accumulo/tserver.pid or $ACCUMULO_HOME/tserver.pid), for
the following benefits:
> # Identify running services on a machine without executing and parsing the system process
list, so stop scripts can kill them when they are unresponsive.
> # Prevent multiple instances of the same application from starting up (an environment
variable for the location of the PIDfile can be used to allow multiple instances if it is
desirable to do so).
> # Potentially provide an alternate mechanism for terminating a process by deleting its
PIDfile rather than its lock in Zookeeper.



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

Mime
View raw message