Return-Path: X-Original-To: apmail-gearpump-dev-archive@minotaur.apache.org Delivered-To: apmail-gearpump-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AB4EA197B6 for ; Thu, 28 Apr 2016 09:27:15 +0000 (UTC) Received: (qmail 31992 invoked by uid 500); 28 Apr 2016 09:27:15 -0000 Delivered-To: apmail-gearpump-dev-archive@gearpump.apache.org Received: (qmail 31956 invoked by uid 500); 28 Apr 2016 09:27:15 -0000 Mailing-List: contact dev-help@gearpump.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@gearpump.incubator.apache.org Delivered-To: mailing list dev@gearpump.incubator.apache.org Received: (qmail 31945 invoked by uid 99); 28 Apr 2016 09:27:15 -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; Thu, 28 Apr 2016 09:27:15 +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 CDB3D1804F1 for ; Thu, 28 Apr 2016 09:27:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.021 X-Spam-Level: X-Spam-Status: No, score=-4.021 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] 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 OsNme3fCa9Tn for ; Thu, 28 Apr 2016 09:27:14 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id 8DBF85F33E for ; Thu, 28 Apr 2016 09:27:13 +0000 (UTC) Received: (qmail 31811 invoked by uid 99); 28 Apr 2016 09:27:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Apr 2016 09:27:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0051F2C0451 for ; Thu, 28 Apr 2016 09:27:13 +0000 (UTC) Date: Thu, 28 Apr 2016 09:27:12 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@gearpump.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (GEARPUMP-7) Master members are not updated if a master is shutdown MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/GEARPUMP-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261844#comment-15261844 ] ASF GitHub Bot commented on GEARPUMP-7: --------------------------------------- GitHub user huafengw opened a pull request: https://github.com/apache/incubator-gearpump/pull/8 fix GEARPUMP-7 Master members are not updated if a master is shutdown On behalf of Xiang You can merge this pull request into a Git repository by running: $ git pull https://github.com/huafengw/incubator-gearpump fix_GEARPUMP-7 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-gearpump/pull/8.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #8 ---- commit add48f7e2babc0c854a7e95c567814679dc5dda7 Author: huafengw Date: 2016-04-28T09:07:16Z fix GEARPUMP-7 Master members are not updated if a master is shutdown ---- > Master members are not updated if a master is shutdown > ------------------------------------------------------ > > Key: GEARPUMP-7 > URL: https://issues.apache.org/jira/browse/GEARPUMP-7 > Project: Apache Gearpump > Issue Type: Bug > Components: Dashboard > Reporter: Manu Zhang > Assignee: Manu Zhang > Attachments: GEARPUMP-7.patch > > > The issue is reported by QiShu from [user group | https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/gearpump-user/hEGwKRxQywI/3sPZlXqEAwAJ]. If multiple masters are launched for HA, and one of them is shut down, the master members item on the master page of dashboard is not updated. > Or better, could we prompt user that which master has been down? After all the masters down, could we at least show some helpful information on the dashboard instead of going blank ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)