You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Patrick Rhomberg (JIRA)" <ji...@apache.org> on 2018/07/16 17:49:00 UTC

[jira] [Resolved] (GEODE-5295) Improve error reporting in ClusterStartupRule await methods

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

Patrick Rhomberg resolved GEODE-5295.
-------------------------------------
    Resolution: Fixed

> Improve error reporting in ClusterStartupRule await methods
> -----------------------------------------------------------
>
>                 Key: GEODE-5295
>                 URL: https://issues.apache.org/jira/browse/GEODE-5295
>             Project: Geode
>          Issue Type: Improvement
>            Reporter: Patrick Rhomberg
>            Assignee: Patrick Rhomberg
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The family of methods that wait until the cluster's gateways / regions / disk stores are ready will occasionally hang, having a number not equal to the expected number of beans.  In these cases, it unclear if the number of expected element beans is too few (indicating a delay or failure to start) or too many (indicating a failure to destroy a previous test).
> Failure reporting should be improved to indicate the nature of failure.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)