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

Posted to issues@metron.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/17 14:44:41 UTC

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

    [ https://issues.apache.org/jira/browse/METRON-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930061#comment-15930061 ] 

ASF GitHub Bot commented on METRON-670:
---------------------------------------

Github user nickwallen commented on the issue:

    https://github.com/apache/incubator-metron/pull/422
  
    No longer needed.


> 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.15#6346)