[
https://issues.apache.org/jira/browse/METRON-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859917#comment-15859917
]
ASF GitHub Bot commented on METRON-670:
---------------------------------------
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/422
All of these files will go away as a result of
[PR-436](https://github.com/apache/incubator-metron/pull/436). Would you guys
be willing to hold off until I can get it completed and through the process?
> 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)
