Return-Path: X-Original-To: apmail-helix-commits-archive@minotaur.apache.org Delivered-To: apmail-helix-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1698818B6A for ; Thu, 14 Jan 2016 23:22:42 +0000 (UTC) Received: (qmail 20250 invoked by uid 500); 14 Jan 2016 23:22:42 -0000 Delivered-To: apmail-helix-commits-archive@helix.apache.org Received: (qmail 20212 invoked by uid 500); 14 Jan 2016 23:22:42 -0000 Mailing-List: contact commits-help@helix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@helix.apache.org Delivered-To: mailing list commits@helix.apache.org Received: (qmail 20203 invoked by uid 99); 14 Jan 2016 23:22:41 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jan 2016 23:22:41 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 8889CC01A9 for ; Thu, 14 Jan 2016 23:22:41 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.427 X-Spam-Level: X-Spam-Status: No, score=0.427 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.554, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 6F61C7QPKX0t for ; Thu, 14 Jan 2016 23:22:41 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with SMTP id 97BCD43F56 for ; Thu, 14 Jan 2016 23:22:40 +0000 (UTC) Received: (qmail 20195 invoked by uid 99); 14 Jan 2016 23:22:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jan 2016 23:22:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C26FF2C14F7 for ; Thu, 14 Jan 2016 23:22:39 +0000 (UTC) Date: Thu, 14 Jan 2016 23:22:39 +0000 (UTC) From: "Marco P. (JIRA)" To: commits@helix.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HELIX-625) Provide mechanism to react to disconnection due to flapping MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Marco P. created HELIX-625: ------------------------------ Summary: Provide mechanism to react to disconnection due to flapping Key: HELIX-625 URL: https://issues.apache.org/jira/browse/HELIX-625 Project: Apache Helix Issue Type: Improvement Components: helix-core Affects Versions: 0.7.1, 0.7.2, 0.6.x, master Reporter: Marco P. Priority: Minor ZKHelixManager can detect an instance flapping and shut down. https://github.com/apache/helix/blob/helix-0.6.x/helix-core/src/main/java/org/apache/helix/manager/zk/ZKHelixManager.java#L808-L812 Currently there is no mechanism for the application to learn about this event (and react to it). The application will be "silently" excluded from participation, stop receiving notifications, updates, etc. A mechanism should exist for the application to be notified, allowing it to react in the appropriate application-specific way (ignore, shutdown, restart, raise alert, ...). -- This message was sent by Atlassian JIRA (v6.3.4#6332)