Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3F6B5CFAE for ; Wed, 13 Jun 2012 01:13:43 +0000 (UTC) Received: (qmail 81243 invoked by uid 500); 13 Jun 2012 01:13:43 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 81209 invoked by uid 500); 13 Jun 2012 01:13:43 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 81197 invoked by uid 99); 13 Jun 2012 01:13:43 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2012 01:13:43 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id CA8AD141BF8 for ; Wed, 13 Jun 2012 01:13:42 +0000 (UTC) Date: Wed, 13 Jun 2012 01:13:42 +0000 (UTC) From: "Aaron T. Myers (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <874910513.10122.1339550022833.JavaMail.jiratomcat@issues-vm> In-Reply-To: <213845813.54387.1339191204537.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HDFS-3518) Provide API to check HDFS operational state MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294045#comment-13294045 ] Aaron T. Myers commented on HDFS-3518: -------------------------------------- Hey Nicholas, patch looks pretty good to me. Two comments: # Perhaps this method could reasonably be added to o.a.h.hdfs.client.HdfsAdmin? # This won't work in an HA setup at the moment since DistributedFileSystem#setSafeMode does not perform client failover, per HDFS-3507. Presumably a user writing against the isHealthy API would like it to return success without considering how many NNs are in play. We might want to wait for resolution of that issue before we introduce this new API that we know won't work as intended. > Provide API to check HDFS operational state > ------------------------------------------- > > Key: HDFS-3518 > URL: https://issues.apache.org/jira/browse/HDFS-3518 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs client > Reporter: Bikas Saha > Assignee: Tsz Wo (Nicholas), SZE > Attachments: h3518_20120611.patch > > > This will improve the usability of JobTracker safe mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira