Tomasz Lasica created CASSANDRA-16405:
-----------------------------------------
Summary: Handle both TimeoutError and NodeError when expecting
node start failure
Key: CASSANDRA-16405
URL: https://issues.apache.org/jira/browse/CASSANDRA-16405
Project: Cassandra
Issue Type: Improvement
Components: Test/dtest/python
Reporter: Tomasz Lasica
Assignee: Tomasz Lasica
Fix For: 2.2.20, 3.0.24, 3.11.10, 4.0-beta5, 4.0
*Summary*
Node start timeouts should be explicitly extended to more than default 90s
(boostrap with reset state, replace node tests) because the default 90s will
start to work after ccm changes.
*Why we need this change*
There is a bug in [https://github.com/riptano/ccm] that node.start() timeout
(or more precisely node.wait_for_binary_proto() timeout is in practice 600s.
This is the time to wait for certain log message:
[https://github.com/riptano/ccm/blob/484476494bda6d71f895826358722a7b1c47a3cf/ccmlib/node.py#L642|https://github.com/riptano/ccm/blob/cassandra-test/ccmlib/node.py#L642]
This bug will be fixed by: [https://github.com/riptano/ccm/pull/725]
*Proposed improvement*
Explicitly raise node start timeout to 120s or 180s (depending on the scenario)
by using existing `Node` api to provide timeout as int (in seconds) instead of
bool.
Note that this is available after [https://github.com/riptano/ccm/pull/725] is
merged but should not break test logic before it is merged.
*PR*
[https://github.com/apache/cassandra-dtest/pull/113/files]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
