Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D60D22009D9 for ; Thu, 19 May 2016 21:18:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D4A06160A00; Thu, 19 May 2016 19:18:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2B8C61609AE for ; Thu, 19 May 2016 21:18:14 +0200 (CEST) Received: (qmail 70537 invoked by uid 500); 19 May 2016 19:18:13 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 70513 invoked by uid 99); 19 May 2016 19:18:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2016 19:18:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D8F642C1F61 for ; Thu, 19 May 2016 19:18:12 +0000 (UTC) Date: Thu, 19 May 2016 19:18:12 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-925) Launch scripts should use a PIDfile MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 19 May 2016 19:18:15 -0000 [ 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)