[
https://issues.apache.org/jira/browse/METRON-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834708#comment-15834708
]
ASF GitHub Bot commented on METRON-670:
---------------------------------------
GitHub user nickwallen opened a pull request:
https://github.com/apache/incubator-metron/pull/422
METRON-670 Monit Incorrectly Reports Status
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.
Added 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 was tested in 'Quick Dev' and made starting, stopping and reporting
status of the topologies using Monit work much better. Previously Monit would
erroneously report some of the topologies as not running when they were. This
would also interfere with your ability to start/stop the same topologies.
For example, starting all of the services required to consume Bro telemetry
works much better with this change.
```
monit -g bro start
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickwallen/incubator-metron METRON-670
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/422.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #422
----
commit adf86d7f8c536d26e9d078768ad8e158fe33bbf2
Author: Nick Allen <[email protected]>
Date: 2017-01-23T14:51:27Z
METRON-670 Monit Incorrectly Reports Status
----
> 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
>
> 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)
