From dev-return-935-archive-asf-public=cust-asf.ponee.io@fluo.apache.org Fri Dec 13 07:11:13 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 4277618064E for ; Fri, 13 Dec 2019 08:11:13 +0100 (CET) Received: (qmail 43758 invoked by uid 500); 13 Dec 2019 07:11:12 -0000 Mailing-List: contact dev-help@fluo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fluo.apache.org Delivered-To: mailing list dev@fluo.apache.org Received: (qmail 43746 invoked by uid 99); 13 Dec 2019 07:11:12 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Dec 2019 07:11:12 +0000 Received: from mail-qt1-f181.google.com (mail-qt1-f181.google.com [209.85.160.181]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 2951B4FBC for ; Fri, 13 Dec 2019 07:11:12 +0000 (UTC) Received: by mail-qt1-f181.google.com with SMTP id b3so1467422qti.10 for ; Thu, 12 Dec 2019 23:11:12 -0800 (PST) X-Gm-Message-State: APjAAAXcOTplh0rQB6EcOiACA2WQ1nUfcxQ/UfCGOSe39HS89F/nerza SVbtKektxgN3FzouJ82flZORnEZPxHRdXVJcMIc= X-Google-Smtp-Source: APXvYqxWnc3NndX4Dls6yyIXdPn+w9LkOhpxXoKp0b08Jn778+AC+NlKYlxAknQHIEQ5EO9TGR7bE3b9X5grSNaTs4w= X-Received: by 2002:ac8:3234:: with SMTP id x49mr11173115qta.209.1576221071864; Thu, 12 Dec 2019 23:11:11 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Christopher Date: Fri, 13 Dec 2019 02:10:55 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Run Accumulo and Hadoop services under systemd To: fluo-dev Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Aishwarya, I'm interested in the details. Are these just for Muchos, or is the intent to propose changes to Accumulo's scripts as well? I assume the former, since you're asking in the Fluo mailing list, but if it's also the latter, I may have more follow-up questions or suggestions wearing an Accumulo PMC hat instead of a Fluo PMC hat. On Thu, Dec 12, 2019 at 2:52 PM Aishwarya Thangappa wrote: > > Hi everyone, > > While using fluo-muchos to deploy an Accumulo cluster, we recognized the = need for various Accumulo and Hadoop services to be run under a service man= ager like systemd which will ensure that all these services are brought up = correctly in the event of VM / OS reboots / cold starts. We have made the r= equired changes for this and would like to contribute it back to the commun= ity if there is any interest around it. > > Summarizing what we have done: > > * Crafted separate systemd unit files for Accumulo (master, monitor, = gc, traser, tserver), Hadoop (journalnode, namenode, datanode, resourcemana= ger, nodemanager, zkfc) and Zookeeper services. > * All of these unit files will be copied to the respective nodes' /et= c/systemd/system directory; the services will then be started and enabled b= y ansible systemd module. > * In case of num_tservers > 1, multiple tserver systemd units will be= copied to the node and each will be independently managed. > * Also made necessary changes to the existing cluster-wide scripts in= cluding accumulo_cluster, accumulo_service, start_dfs, start_yarn etc., to = have them work seamlessly with sytemd. > > Is there an appetite to look at the details? If so, we can post a PR or i= f there are any feedbacks and other considerations, please let us know and = we can discuss them. > > Thanks, > Aishwarya >