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 DB442200D06 for ; Mon, 25 Sep 2017 19:51:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D9E581609E9; Mon, 25 Sep 2017 17:51:04 +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 2B90B1609B5 for ; Mon, 25 Sep 2017 19:51:04 +0200 (CEST) Received: (qmail 4170 invoked by uid 500); 25 Sep 2017 17:51:03 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 4158 invoked by uid 99); 25 Sep 2017 17:51:03 -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; Mon, 25 Sep 2017 17:51:03 +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 D515DDC60B for ; Mon, 25 Sep 2017 17:51:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, 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 Xoh8RdL7JbGD for ; Mon, 25 Sep 2017 17:51: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 E3DAD5F5FD for ; Mon, 25 Sep 2017 17:51:01 +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 29278E0E9A for ; Mon, 25 Sep 2017 17:51: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 5668424246 for ; Mon, 25 Sep 2017 17:51:00 +0000 (UTC) Date: Mon, 25 Sep 2017 17:51:00 +0000 (UTC) From: "Bharat Viswanadham (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-12498) Journal Syncer is not started in Federated + HA cluster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 25 Sep 2017 17:51:05 -0000 [ https://issues.apache.org/jira/browse/HDFS-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179428#comment-16179428 ] Bharat Viswanadham commented on HDFS-12498: ------------------------------------------- Now if dfs.shared.edits.dir is suffixed with nameserviceId or (namserviceId along with namenodeId) journal syncer is getting started. Tested it on federated cluster setup. > Journal Syncer is not started in Federated + HA cluster > ------------------------------------------------------- > > Key: HDFS-12498 > URL: https://issues.apache.org/jira/browse/HDFS-12498 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: Bharat Viswanadham > Assignee: Bharat Viswanadham > Attachments: HDFS-12498.01.patch, HDFS-12498.02.patch, hdfs-site.xml > > > Journal Syncer is not getting started in HDFS + Federated cluster, when dfs.shared.edits.dir.<> is provided, instead of dfs.namenode.shared.edits.dir > *Log Snippet:* > {code:java} > 2017-09-19 21:42:40,598 WARN org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not construct Shared Edits Uri > 2017-09-19 21:42:40,598 WARN org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Other JournalNode addresses not available. Journal Syncing cannot be done > 2017-09-19 21:42:40,598 WARN org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Failed to start SyncJournal daemon for journal ns1 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org