[
https://issues.apache.org/jira/browse/HADOOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated HADOOP-3153:
--------------------------------------------
Attachment: HADOOP-3153
Attaching a patch. This results in the following behaviour:
- Any operation fails right away, when user cluster state file has no read
permissions.
- Allocation fails if user cluster state has no write permissions.
- Deallocation deallocates the cluster, but doesn't(cannot) update user
cluster state when the file has no write permissions. After this, info and list
still report old clusters, but saying information cannot be found about the
clusters. Agreeable. (?)
- The last step of allocation, writing to state file, is now enclosed in a
try-catch block to handle any unknown error conditions. Not sure when this can
trigger, but putting it just in case.
Added test cases. Thinks to check - behavior, error messages and error codes.
Deallocation with invalid cluster state file couldn't have a test case now,
'coz of lack of enough testing framework in place to do this (a successful
allocation followed by a failing deallocate).
> [HOD] Hod should deallocate cluster if there's a problem in writing
> information to the state file
> -------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3153
> URL: https://issues.apache.org/jira/browse/HADOOP-3153
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/hod
> Affects Versions: 0.16.0
> Reporter: Hemanth Yamijala
> Assignee: Vinod Kumar Vavilapalli
> Fix For: 0.17.0
>
> Attachments: HADOOP-3153
>
>
> Consider a scenario where hod runs allocate successfully, but isn't able to
> save teh allocated information to the clusters.state file. In such a case, it
> gets an error and exits. But the cluster remains allocated, and unfortunately
> the user cannot deallocate the cluster now unless he knows the cluster
> directory.
> It is better if HOD can deallocate the cluster in such an error condition.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
