kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ewe...@apache.org
Subject [kafka] branch 1.0 updated: MINOR: Increase timeout for starting JMX tool (#5735)
Date Fri, 05 Oct 2018 00:05:49 GMT
This is an automated email from the ASF dual-hosted git repository.

ewencp pushed a commit to branch 1.0
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/1.0 by this push:
     new 53d76c7  MINOR: Increase timeout for starting JMX tool (#5735)
53d76c7 is described below

commit 53d76c73587f751923dfca83178847c9d3deb338
Author: Randall Hauch <rhauch@gmail.com>
AuthorDate: Wed Oct 3 10:56:44 2018 -0500

    MINOR: Increase timeout for starting JMX tool (#5735)
    
    In some tests, the check monitoring the JMX tool log output doesn’t quite wait long
enough before failing. Increasing the timeout from 10 to 20 seconds.
---
 tests/kafkatest/services/monitor/jmx.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/kafkatest/services/monitor/jmx.py b/tests/kafkatest/services/monitor/jmx.py
index 6f6e221..a64842c 100644
--- a/tests/kafkatest/services/monitor/jmx.py
+++ b/tests/kafkatest/services/monitor/jmx.py
@@ -83,7 +83,7 @@ class JmxMixin(object):
 
         self.logger.debug("%s: Start JmxTool %d command: %s" % (node.account, idx, cmd))
         node.account.ssh(cmd, allow_fail=False)
-        wait_until(lambda: self._jmx_has_output(node), timeout_sec=10, backoff_sec=.5, err_msg="%s:
Jmx tool took too long to start" % node.account)
+        wait_until(lambda: self._jmx_has_output(node), timeout_sec=20, backoff_sec=.5, err_msg="%s:
Jmx tool took too long to start" % node.account)
         self.started[idx-1] = True
 
     def _jmx_has_output(self, node):


Mime
View raw message