Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 7 Mar 2012 16:40:58 +0000 (UTC)
From: "Daryn Sharp (Commented) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1517260960.34746.1331138458122.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <611677435.30235.1331075518988.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-8146) FsShell commands cannot be
 interrupted
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-8146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224490#comment-13224490 ] 

Daryn Sharp commented on HADOOP-8146:
-------------------------------------

# I think it's overall a good idea, but dfsadmin is still subclassing FsShell/Command.  It's not using the rest of the logic, but I'd rather not change nor risk destabilizing that command at this time.  Would you be willing to file a new jira?
# I wish I could, but the commands do not have public visibility to prevent direct instantiation.  All the loops for processing paths including a try loop that catches IOException, so interrupts are always converted to exceptions.  The 2nd interrupt test does already exercise recursion into a directory.

Let me know if you want me to make further changes.
                
> FsShell commands cannot be interrupted
> --------------------------------------
>
>                 Key: HADOOP-8146
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8146
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>         Attachments: HADOOP-8146.patch
>
>
> Control-c is apparently generating {{InterruptedIOExceptions}}.  The path processing loop traps {{IOException}}, displays the error, and moves to the next path.  This means that recursive operations cannot be aborted.

--
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