Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <1024226578.1261157418865.JavaMail.jira@brutus>
Date: Fri, 18 Dec 2009 17:30:18 +0000 (UTC)
From: "Tom White (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Updated: (HDFS-844) Log the filename when file locking fails
In-Reply-To: <1642268817.1261157298123.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White updated HDFS-844:
---------------------------

    Attachment: HDFS-844.patch

Patch which adds a log line. No new tests.

> Log the filename when file locking fails
> ----------------------------------------
>
>                 Key: HDFS-844
>                 URL: https://issues.apache.org/jira/browse/HDFS-844
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Tom White
>            Assignee: Tom White
>         Attachments: HDFS-844.patch
>
>
> When the storage lock cannot be acquired in StorageDirectory.tryLock() the the error message does not show the storage volume that was at fault. The log message is very generic:
> {code}
> common.Storage: java.io.IOException: Input/output error
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.