Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9338710402 for ; Mon, 12 Jan 2015 22:49:33 +0000 (UTC) Received: (qmail 45016 invoked by uid 500); 12 Jan 2015 22:49:35 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 44979 invoked by uid 500); 12 Jan 2015 22:49:35 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 44967 invoked by uid 99); 12 Jan 2015 22:49:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jan 2015 22:49:35 +0000 Date: Mon, 12 Jan 2015 22:49:35 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ACCUMULO-3472) VolumeImpl.isValidPath not working as intended MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Josh Elser created ACCUMULO-3472: ------------------------------------ Summary: VolumeImpl.isValidPath not working as intended Key: ACCUMULO-3472 URL: https://issues.apache.org/jira/browse/ACCUMULO-3472 Project: Accumulo Issue Type: Bug Reporter: Josh Elser Assignee: Josh Elser Fix For: 1.6.2, 1.7.0 I see the following often in my tserver logs as a part of normal operations: {noformat} 2015-01-12 17:11:15,322 [fs.VolumeManagerImpl] DEBUG: Found candidate Volumes for Path but none of the Paths are valid on the candidates: hdfs://namenode:8020/apps/accumulo/tables/2/t-00004ju/A00004o2.rf_tmp 2015-01-12 17:11:15,323 [fs.VolumeManagerImpl] DEBUG: Could not determine volume for Path: hdfs://namenode:8020/apps/accumulo/tables/2/t-00004ju/A00004o2.rf_tmp {noformat} We shouldn't be seeing those error messages, nor do we need two messages for the single case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)