Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5860D1035D for ; Mon, 24 Feb 2014 20:17:25 +0000 (UTC) Received: (qmail 99867 invoked by uid 500); 24 Feb 2014 20:17:22 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 99764 invoked by uid 500); 24 Feb 2014 20:17:21 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 99756 invoked by uid 99); 24 Feb 2014 20:17:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 20:17:21 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of magnito@gmail.com designates 209.85.128.179 as permitted sender) Received: from [209.85.128.179] (HELO mail-ve0-f179.google.com) (209.85.128.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 20:17:16 +0000 Received: by mail-ve0-f179.google.com with SMTP id oz11so974948veb.38 for ; Mon, 24 Feb 2014 12:16:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=xEY3cEoZadw8SNGmCb4IOnihdEeFazHAhb0SQCA2xLI=; b=NNnBq87wmA0lNoTYWOisXreyzHxk3vuiF9owiUX89QkrMlyapNsamPkNNTHfvAoL7/ RQc+S6hjhPf2DwVj4h6X+Dx32qK9SlRyrK4wDBcf1UGV+XWzf631YibBWog+s6xKG9K/ hHtejyeC4ETTYkkrGdniWexlOXxjvWLidEXU9IWXOljGpq8I3DKMgUn5g5dNeTOmREHk maPe65exKtymPvEd4F2C/cQDsNCVlafQD3hyRI6IKngapjDtlYJca/nbi9bfcXqTIrW3 z3xOZCDl5OwRC0x+mcLtT7pvuTh6SLLFtPgMJK2OIijCGgTF1iXfoTELYU1SetL+In0T nzHg== MIME-Version: 1.0 X-Received: by 10.220.164.80 with SMTP id d16mr13707756vcy.15.1393273015372; Mon, 24 Feb 2014 12:16:55 -0800 (PST) Received: by 10.58.187.162 with HTTP; Mon, 24 Feb 2014 12:16:55 -0800 (PST) In-Reply-To: References: Date: Mon, 24 Feb 2014 12:16:55 -0800 Message-ID: Subject: Re: Question about dead datanode From: Jack Levin To: "user@hbase.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I will do that. -Jack On Mon, Feb 24, 2014 at 6:23 AM, Steve Loughran wrote: > that's a very old version of cloudera's branch you are working with there; > patching that is not a good way to go, as you are on the slippery slope of > having your own private branch and all the costs of it. > > It looks like dead node logic has -> DFSInputStream, where it is still > instance-specific: > > /* XXX Use of CocurrentHashMap is temp fix. Need to fix > * parallel accesses to DFSInputStream (through ptreads) properly */ > private final ConcurrentHashMap deadNodes = > new ConcurrentHashMap(); > > This implies the problem still exists -and the opportunity to fix it -but > you will need to modify your patch to apply to hadoop trunk, ideally think > of a test, then submit a patch to the HDFS project on JIRA. > > > On 19 February 2014 04:48, Stack wrote: > >> On Sat, Feb 15, 2014 at 8:01 PM, Jack Levin wrote: >> >> > Looks like I patched it in DFSClient.java, here is the patch: >> > https://gist.github.com/anonymous/9028934 >> > >> > .... >> >> >> > I moved 'deadNodes' list outside as global field that is accessible by >> > all running threads, so at any point datanode does go down, each >> > thread is basically informed that the datanode _is_ down. >> > >> >> We need to add something like this to current versions of DFSClient, a >> global status, so each stream does not have to discover bad DNs for itself. >> St.Ack >> > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You.