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 DB824200C22 for ; Tue, 21 Feb 2017 23:00:49 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id DA1EA160B4F; Tue, 21 Feb 2017 22:00:49 +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 2DEF9160B68 for ; Tue, 21 Feb 2017 23:00:49 +0100 (CET) Received: (qmail 42746 invoked by uid 500); 21 Feb 2017 22:00:48 -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 42586 invoked by uid 99); 21 Feb 2017 22:00:47 -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; Tue, 21 Feb 2017 22:00:47 +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 9031FC7DD7 for ; Tue, 21 Feb 2017 22:00:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.999 X-Spam-Level: X-Spam-Status: No, score=0.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.001] 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 nQ0qTElF_Y5O for ; Tue, 21 Feb 2017 22:00:47 +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 6E78B5F1B8 for ; Tue, 21 Feb 2017 22:00:46 +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 B7805E0012 for ; Tue, 21 Feb 2017 22:00:45 +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 74C3D24121 for ; Tue, 21 Feb 2017 22:00:45 +0000 (UTC) Date: Tue, 21 Feb 2017 22:00:45 +0000 (UTC) From: "James Clampffer (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-11437) libhdfs++: Handler for FileSystem async connect can be invoked before successful communication with active NN MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 21 Feb 2017 22:00:50 -0000 James Clampffer created HDFS-11437: -------------------------------------- Summary: libhdfs++: Handler for FileSystem async connect can be invoked before successful communication with active NN Key: HDFS-11437 URL: https://issues.apache.org/jira/browse/HDFS-11437 Project: Hadoop HDFS Issue Type: Sub-task Reporter: James Clampffer Assignee: James Clampffer The handler provided to FileSystem::Connect can be invoked as soon as the FS makes a connection to the standby NN rather than waiting until it connects to the active NN. This allows RPC requests to be enqueued before a real connection is made and if the active NN isn't reachable for some reason the only way to cancel is to delete the FS from another thread which kills all pending requests. The underlying issue is that currently the only thing that must happen for the connect handler to be invoked is a successful handshake with a NN. Connecting to the standby NN and receiving a StandbyException satisfies this requirement but it should wait until it is able to get a handshake from the active NN. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org