You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2008/04/02 14:57:24 UTC
[jira] Created: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
[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
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.
[jira] Updated: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Milind Bhandarkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milind Bhandarkar updated HADOOP-3153:
--------------------------------------
Fix Version/s: (was: 0.16.3)
0.17.0
> [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
>
>
> 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.
[jira] Updated: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala updated HADOOP-3153:
-------------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I committed this patch to trunk, and Devaraj committed it to the 0.17 branch. Thanks, Vinod !
> [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, HADOOP-3153.1, HADOOP-3153.2
>
>
> 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.
[jira] Commented: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587135#action_12587135 ]
Hemanth Yamijala commented on HADOOP-3153:
------------------------------------------
Basic fix seem right.
Some comments:
- If the $HOME/.hod directory does not exist, (and so the clusters.state file does not exist), allocate is not working.
- I think we can make some small changes to the error messages. Currently, in the error scenario, for allocate we say:
Invalid Permissions on clusters' data file : /home/yhemanth/.hod/clusters.state. It has to be a readable file.
Instead, we can say:
Requested operation cannot be performed. Cannot read /home/yhemanth/.hod/clusters.state: Permission denied.
This is somewhat similar to what Unix errors report.
Likewise, for deallocate, when you don't have write permissions, we say:
Invalid Permissions on clusters' data file : /home/yhemanth/.hod/clusters.state. It has to be a writable file. info and list operations might show old cluster data.
Instead, we can say:
Cannot update /home/yhemanth/.hod/clusters.state: Permission denied.\n Cluster is deallocated, but info and list operations might show incorrect information.
- In the except block of the last part of the allocate command, the deallocation is still not happening, right ? It should be, as per your comment ?
Minor points:
- For the checkStateFile, I think we can pass in some const strings instead of the hardcoded numbers. In fact, it would be great if we can reuse os.R_OK etc. Can we not OR os.R_OK and os.W_OK to accomodate mode 3 ?
- Likewise the error strings, if possible should be only at one place. That way, it will be easier to change.
Test cases:
- Move setupConf to a library type function.. maybe in a util class in the same module.
- One more test case I can think of is what happens if the cluster state directory does not have write and execute permissions. This is actually the scenario that we have fixed
> [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.
[jira] Updated: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala updated HADOOP-3153:
-------------------------------------
Fix Version/s: 0.16.3
> [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.16.3
>
>
> 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.
[jira] Commented: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587970#action_12587970 ]
Hudson commented on HADOOP-3153:
--------------------------------
Integrated in Hadoop-trunk #457 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/457/])
> [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, HADOOP-3153.1, HADOOP-3153.2
>
>
> 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.
[jira] Assigned: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli reassigned HADOOP-3153:
-----------------------------------------------
Assignee: Vinod Kumar Vavilapalli
> [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
>
> 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.
[jira] Updated: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated HADOOP-3153:
--------------------------------------------
Status: Patch Available (was: Open)
> [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, HADOOP-3153.1, HADOOP-3153.2
>
>
> 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.
[jira] Updated: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ 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.1
Attaching a second patch incorporating above suggestions.
- Allocate works now, even if .hod directory does not exist.
- Made changes to error messages.
- Incorporated minor points and suggestions for changes in test-cases.
- Now, deallocation happens when the except block of the last part of the allocate command is triggered. Tested this by putting in a hard-coded exception, and verified that cluster is deallocated.
- To implement the above, re-factored code in hadoop.py a bit. Tested the re-factored code too(by giving an interrupt after ringmaster comes up).
- Made changes to error codes so that 1 is returned when failing because of an invalid state file. ( <1><Configuration error><Incorrect configuration values specified in hodrc, or other errors related to HOD configuration. The error messages in this case must be sufficient to debug and fix the problem> )
> [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, HADOOP-3153.1
>
>
> 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.
[jira] Commented: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587699#action_12587699 ]
Hemanth Yamijala commented on HADOOP-3153:
------------------------------------------
+1. Patch looks good now.
> [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, HADOOP-3153.1, HADOOP-3153.2
>
>
> 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.
[jira] Updated: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587549#action_12587549 ]
Hemanth Yamijala commented on HADOOP-3153:
------------------------------------------
- I am not sure we need the refactoring. Why can't we call hadoopCluster.deallocate from the except code block ? Even if for some reason we cannot, I think we must refactor this differently.
{noformat}
def shutdown_job(self, ringClient=None):
if ringClient is not None:
self.__log.debug("Calling rm.stop()")
ringClient.stopRM()
self.__log.debug("Returning from rm.stop()")
self.__log.info("Job Shutdown by informing ringmaster.")
else:
self.delete_job(self.jobId)
self.__log.info("Job %s removed from queue directly." % self.jobId)
{noformat}
And there must be a way to get the ringClient from hadoopCluster in hodRunner.py
- In checkStateFile: I think we should check that self.__store is writable. Alternatively, can we check if the file does not exist, by using errno to differentiate permission errors.
- Provide an accessor for _hodState__stateFile in hodState and use that.
- testAllocateWithInvalidStateStore - we can add a test case where the directory has no write permissions.
> [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, HADOOP-3153.1
>
>
> 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.
[jira] Commented: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587868#action_12587868 ]
Hadoop QA commented on HADOOP-3153:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12379829/HADOOP-3153.2
against trunk revision 645773.
@author +1. The patch does not contain any @author tags.
tests included +1. The patch appears to include 3 new or modified tests.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler warnings.
release audit +1. The applied patch does not generate any new release audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2204/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2204/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2204/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2204/console
This message is automatically generated.
> [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, HADOOP-3153.1, HADOOP-3153.2
>
>
> 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.
[jira] Updated: (HADOOP-3153) [HOD] Hod should deallocate cluster
if there's a problem in writing information to the state file
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ 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.2
* Knocking off the refactoring code. Using hadoopCluster.deallocate instead, as suggested.
* Incorporated the rest of the changes suggested.
Attaching patch.
> [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, HADOOP-3153.1, HADOOP-3153.2
>
>
> 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.