hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2848) [HOD] If a cluster directory is deleted, hod -o list must show it, and deallocate should work.
Date Tue, 18 Mar 2008 17:47:25 GMT

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

Hemanth Yamijala updated HADOOP-2848:
-------------------------------------

    Attachment: 2848.1.patch

Vinod, thanks for the review. 

The attached patch fixes the problems identified in the review. In the process, I modified
the error codes and messages for some of the operations so that they are now consistent.

The behavior of the list, info and deallocate commands for a directory that was previously
allocated, but was subsequently deleted, or recreated would be the same in that we would identify
that this was a previously allocated directory and give out a message accordingly. 

The allocate command will now fail if the cluster directory was found to be allocated (or
recreated)

If an invalid directory is given to info or deallocate, it would just print a message saying
the directory is invalid and fail.

> [HOD] If a cluster directory is deleted, hod -o list must show it, and deallocate should
work.
> ----------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2848
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2848
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/hod
>    Affects Versions: 0.16.0
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>             Fix For: 0.17.0
>
>         Attachments: 2848.1.patch, 2848.patch
>
>
> Currently if the cluster directory is deleted, all state about the cluster is lost. While
this in itself is not a problem, at least recovery in the sense of being able to list the
torque job id and deallocation to clear up the nodes should happen correctly.

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


Mime
View raw message