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 F0331200D23 for ; Thu, 5 Oct 2017 00:02:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EE60C160BDB; Wed, 4 Oct 2017 22:02:05 +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 46231160BD7 for ; Thu, 5 Oct 2017 00:02:05 +0200 (CEST) Received: (qmail 78718 invoked by uid 500); 4 Oct 2017 22:02:04 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 78706 invoked by uid 99); 4 Oct 2017 22:02:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Oct 2017 22:02:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 761CBC7E18 for ; Wed, 4 Oct 2017 22:02:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id MwD03EeWh-D0 for ; Wed, 4 Oct 2017 22:02:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 037FC5FE02 for ; Wed, 4 Oct 2017 22:02:02 +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 2CA55E0F7D for ; Wed, 4 Oct 2017 22:02:01 +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 9165F2430F for ; Wed, 4 Oct 2017 22:02:00 +0000 (UTC) Date: Wed, 4 Oct 2017 22:02:00 +0000 (UTC) From: "Hanisha Koneru (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-12592) JournalNodeSyncer does not discover newly added JournalNodes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 04 Oct 2017 22:02:06 -0000 Hanisha Koneru created HDFS-12592: ------------------------------------- Summary: JournalNodeSyncer does not discover newly added JournalNodes Key: HDFS-12592 URL: https://issues.apache.org/jira/browse/HDFS-12592 Project: Hadoop HDFS Issue Type: Bug Reporter: Hanisha Koneru Assignee: Hanisha Koneru The JournalNodeSyncer, during initialization, gets the list of other journal nodes from the config. All subsequent sync calls are made to these journal nodes. If another journal node is added to the cluster or a journal node is restarted at a different address, then the running journalNodeSyncers would not be aware of the new/ modified journal nodes. We would need to update the shared.edits property in all the journal nodes and restart them for the syncers to work correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org