hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3663) MiniDFSCluster should capture the code path that led to the first ExitException
Date Sun, 15 Jul 2012 19:50:34 GMT

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

Eli Collins updated HDFS-3663:
------------------------------

          Resolution: Fixed
       Fix Version/s: 2.0.1-alpha
    Target Version/s:   (was: 2.0.1-alpha)
        Hadoop Flags: Reviewed
              Status: Resolved  (was: Patch Available)

Thanks for the review ATM. I've committed this and merged to branch-2.
                
> MiniDFSCluster should capture the code path that led to the first ExitException 
> --------------------------------------------------------------------------------
>
>                 Key: HDFS-3663
>                 URL: https://issues.apache.org/jira/browse/HDFS-3663
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 2.0.0-alpha
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>             Fix For: 2.0.1-alpha
>
>         Attachments: hdfs-3663.txt
>
>
> The MiniDFSCluster should capture the code path that led to the first ExitException being
thrown since it's now always available in the logs when an ExitException was unexpected, eg
HDFS-3642.

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

        

Mime
View raw message