You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metron.apache.org by "Casey Stella (JIRA)" <ji...@apache.org> on 2017/01/26 23:10:24 UTC

[jira] [Updated] (METRON-670) Monit Incorrectly Reports Status

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

Casey Stella updated METRON-670:
--------------------------------
    Fix Version/s: 0.3.1

> Monit Incorrectly Reports Status
> --------------------------------
>
>                 Key: METRON-670
>                 URL: https://issues.apache.org/jira/browse/METRON-670
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>             Fix For: 0.3.1
>
>
> In a constrained environment, like 'Quick Dev', Monit will often incorrectly report the status of a Metron topology.  This occurs when the environment is under load and a query of topology status exceeds the default timeout of 30 seconds.  Need to add a parameter so that the timeout for a status check can be extended under these conditions.  This was previously done for starting and stopping a topology, but not for a status checks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)