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 0C5C4200C6F for ; Tue, 9 May 2017 10:52:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0AF69160BC3; Tue, 9 May 2017 08:52:08 +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 4E943160BB3 for ; Tue, 9 May 2017 10:52:07 +0200 (CEST) Received: (qmail 6812 invoked by uid 500); 9 May 2017 08:52:06 -0000 Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hawq.incubator.apache.org Delivered-To: mailing list dev@hawq.incubator.apache.org Received: (qmail 6792 invoked by uid 99); 9 May 2017 08:52:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 May 2017 08:52:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 1CF6B18140E for ; Tue, 9 May 2017 08:52:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id MOikmNSb4JDm for ; Tue, 9 May 2017 08:52:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3F47E5FBBB for ; Tue, 9 May 2017 08:52:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C7C50E0D2F for ; Tue, 9 May 2017 08:52:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2EEA521DF9 for ; Tue, 9 May 2017 08:52:04 +0000 (UTC) Date: Tue, 9 May 2017 08:52:04 +0000 (UTC) From: "Paul Guo (JIRA)" To: dev@hawq.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HAWQ-1460) WAL Send Server process should exit if postmaster on master is killed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 09 May 2017 08:52:08 -0000 Paul Guo created HAWQ-1460: ------------------------------ Summary: WAL Send Server process should exit if postmaster on master is killed Key: HAWQ-1460 URL: https://issues.apache.org/jira/browse/HAWQ-1460 Project: Apache HAWQ Issue Type: Bug Components: Core Reporter: Paul Guo Assignee: Ed Espino Fix For: 2.3.0.0-incubating If we kill the postmaster on master, we will see two processes keep running. pguo 44007 1 0 16:35 ? 00:00:00 postgres: port 5432, master logger process pguo 44014 1 0 16:35 ? 00:00:00 postgres: port 5432, WAL Send Server process Well, maybe we should exit the "WAL Send Server process" so that the processes on master are all gone via checking PostmasterIsAlive() in its loop code. Note in distributed system any process could be killed at any time without any callback, handler etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)