java.lang.AssertionError: Waited 32 seconds instead an expected 30 seconds wait expected [true] but found [false]

DataStax JIRA | Joaquin Casares | 3 years ago
  1. 0

    We're still seeing the same issue with isUp() returning too early. Here are the full stacktraces behind run #116: {CODE} Tests run: 96, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 2,659.05 sec <<< FAILURE! dcAwareRoundRobinTestWithOneRemoteHost(com.datastax.driver.core.LoadBalancingPolicyTest) Time elapsed: 103.163 sec <<< FAILURE! java.lang.IllegalStateException: 127.0.1.5 is not UP after 30s at com.datastax.driver.core.TestUtils.waitFor(TestUtils.java:333) at com.datastax.driver.core.TestUtils.waitFor(TestUtils.java:259) at com.datastax.driver.core.LoadBalancingPolicyTest.dcAwareRoundRobinTestWithOneRemoteHost(LoadBalancingPolicyTest.java:160) reprepareOnNewlyUpNodeNoKeyspaceTest(com.datastax.driver.core.PreparedStatementTest) Time elapsed: 18.34 sec <<< FAILURE! com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (no host was tried) at com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:103) at com.datastax.driver.core.Session$Manager.execute(Session.java:474) at com.datastax.driver.core.Session$Manager.executeQuery(Session.java:510) at com.datastax.driver.core.Session.executeAsync(Session.java:156) at com.datastax.driver.core.Session.execute(Session.java:111) at com.datastax.driver.core.PreparedStatementTest.reprepareOnNewlyUpNodeTest(PreparedStatementTest.java:303) at com.datastax.driver.core.PreparedStatementTest.reprepareOnNewlyUpNodeNoKeyspaceTest(PreparedStatementTest.java:322) reprepareOnNewlyUpNodeTest(com.datastax.driver.core.PreparedStatementTest) Time elapsed: 0 sec <<< FAILURE! com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (no host was tried) at com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:103) at com.datastax.driver.core.Session$Manager.execute(Session.java:474) at com.datastax.driver.core.Session$Manager.executeQuery(Session.java:510) at com.datastax.driver.core.Session.executeAsync(Session.java:151) at com.datastax.driver.core.Session.execute(Session.java:111) at com.datastax.driver.core.Session.execute(Session.java:80) at com.datastax.driver.core.PreparedStatementTest.reprepareOnNewlyUpNodeTest(PreparedStatementTest.java:288) at com.datastax.driver.core.PreparedStatementTest.reprepareOnNewlyUpNodeTest(PreparedStatementTest.java:314) exponentialReconnectionPolicyTest(com.datastax.driver.core.ReconnectionPolicyTest) Time elapsed: 71.494 sec <<< FAILURE! java.lang.AssertionError: Waited 32 seconds instead an expected 30 seconds wait expected [true] but found [false] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertTrue(Assert.java:42) at com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:202) at com.datastax.driver.core.ReconnectionPolicyTest.exponentialReconnectionPolicyTest(ReconnectionPolicyTest.java:82) listenerTest(com.datastax.driver.core.StateListenerTest) Time elapsed: 80.464 sec <<< FAILURE! java.lang.AssertionError: expected [1] but found [2] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertEquals(Assert.java:123) at org.testng.Assert.assertEquals(Assert.java:370) at org.testng.Assert.assertEquals(Assert.java:380) at com.datastax.driver.core.StateListenerTest.listenerTest(StateListenerTest.java:47) Results : Failed tests: LoadBalancingPolicyTest.dcAwareRoundRobinTestWithOneRemoteHost:160 » IllegalState PreparedStatementTest.reprepareOnNewlyUpNodeNoKeyspaceTest:322->reprepareOnNewlyUpNodeTest:303 » NoHostAvailable PreparedStatementTest.reprepareOnNewlyUpNodeTest:314->reprepareOnNewlyUpNodeTest:288 » NoHostAvailable ReconnectionPolicyTest.exponentialReconnectionPolicyTest:82->reconnectionPolicyTest:202 Waited 32 seconds instead an expected 30 seconds wait expected [true] but found [false] StateListenerTest.listenerTest:47 expected [1] but found [2] {CODE} The NoHostAvailableException is the exception that you can use to debug the issue at isUp(). Here is one example: {CODE} at com.datastax.driver.core.PreparedStatementTest.reprepareOnNewlyUpNodeTest(PreparedStatementTest.java:303) waitFor(CCMBridge.IP_PREFIX + "1", cluster); try { assertEquals(session.execute(ps.bind("124")).one().getInt("i"), 18); } {CODE} Which needs this portion in order to return from waitFor(): {CODE} in TestUtils.java private static boolean testHost(Host host, boolean testForDown) { return testForDown ? !host.isUp() : host.isUp(); } {CODE} There you'll see that isUp() should have waited until the binary protocol is up, before continuing on. Let me know if you need any additional information.

    DataStax JIRA | 3 years ago | Joaquin Casares
    java.lang.AssertionError: Waited 32 seconds instead an expected 30 seconds wait expected [true] but found [false]
  2. 0

    We're still seeing the same issue with isUp() returning too early. Here are the full stacktraces behind run #116: {CODE} Tests run: 96, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 2,659.05 sec <<< FAILURE! dcAwareRoundRobinTestWithOneRemoteHost(com.datastax.driver.core.LoadBalancingPolicyTest) Time elapsed: 103.163 sec <<< FAILURE! java.lang.IllegalStateException: 127.0.1.5 is not UP after 30s at com.datastax.driver.core.TestUtils.waitFor(TestUtils.java:333) at com.datastax.driver.core.TestUtils.waitFor(TestUtils.java:259) at com.datastax.driver.core.LoadBalancingPolicyTest.dcAwareRoundRobinTestWithOneRemoteHost(LoadBalancingPolicyTest.java:160) reprepareOnNewlyUpNodeNoKeyspaceTest(com.datastax.driver.core.PreparedStatementTest) Time elapsed: 18.34 sec <<< FAILURE! com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (no host was tried) at com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:103) at com.datastax.driver.core.Session$Manager.execute(Session.java:474) at com.datastax.driver.core.Session$Manager.executeQuery(Session.java:510) at com.datastax.driver.core.Session.executeAsync(Session.java:156) at com.datastax.driver.core.Session.execute(Session.java:111) at com.datastax.driver.core.PreparedStatementTest.reprepareOnNewlyUpNodeTest(PreparedStatementTest.java:303) at com.datastax.driver.core.PreparedStatementTest.reprepareOnNewlyUpNodeNoKeyspaceTest(PreparedStatementTest.java:322) reprepareOnNewlyUpNodeTest(com.datastax.driver.core.PreparedStatementTest) Time elapsed: 0 sec <<< FAILURE! com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (no host was tried) at com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:103) at com.datastax.driver.core.Session$Manager.execute(Session.java:474) at com.datastax.driver.core.Session$Manager.executeQuery(Session.java:510) at com.datastax.driver.core.Session.executeAsync(Session.java:151) at com.datastax.driver.core.Session.execute(Session.java:111) at com.datastax.driver.core.Session.execute(Session.java:80) at com.datastax.driver.core.PreparedStatementTest.reprepareOnNewlyUpNodeTest(PreparedStatementTest.java:288) at com.datastax.driver.core.PreparedStatementTest.reprepareOnNewlyUpNodeTest(PreparedStatementTest.java:314) exponentialReconnectionPolicyTest(com.datastax.driver.core.ReconnectionPolicyTest) Time elapsed: 71.494 sec <<< FAILURE! java.lang.AssertionError: Waited 32 seconds instead an expected 30 seconds wait expected [true] but found [false] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertTrue(Assert.java:42) at com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:202) at com.datastax.driver.core.ReconnectionPolicyTest.exponentialReconnectionPolicyTest(ReconnectionPolicyTest.java:82) listenerTest(com.datastax.driver.core.StateListenerTest) Time elapsed: 80.464 sec <<< FAILURE! java.lang.AssertionError: expected [1] but found [2] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertEquals(Assert.java:123) at org.testng.Assert.assertEquals(Assert.java:370) at org.testng.Assert.assertEquals(Assert.java:380) at com.datastax.driver.core.StateListenerTest.listenerTest(StateListenerTest.java:47) Results : Failed tests: LoadBalancingPolicyTest.dcAwareRoundRobinTestWithOneRemoteHost:160 » IllegalState PreparedStatementTest.reprepareOnNewlyUpNodeNoKeyspaceTest:322->reprepareOnNewlyUpNodeTest:303 » NoHostAvailable PreparedStatementTest.reprepareOnNewlyUpNodeTest:314->reprepareOnNewlyUpNodeTest:288 » NoHostAvailable ReconnectionPolicyTest.exponentialReconnectionPolicyTest:82->reconnectionPolicyTest:202 Waited 32 seconds instead an expected 30 seconds wait expected [true] but found [false] StateListenerTest.listenerTest:47 expected [1] but found [2] {CODE} The NoHostAvailableException is the exception that you can use to debug the issue at isUp(). Here is one example: {CODE} at com.datastax.driver.core.PreparedStatementTest.reprepareOnNewlyUpNodeTest(PreparedStatementTest.java:303) waitFor(CCMBridge.IP_PREFIX + "1", cluster); try { assertEquals(session.execute(ps.bind("124")).one().getInt("i"), 18); } {CODE} Which needs this portion in order to return from waitFor(): {CODE} in TestUtils.java private static boolean testHost(Host host, boolean testForDown) { return testForDown ? !host.isUp() : host.isUp(); } {CODE} There you'll see that isUp() should have waited until the binary protocol is up, before continuing on. Let me know if you need any additional information.

    DataStax JIRA | 3 years ago | Joaquin Casares
    java.lang.AssertionError: Waited 32 seconds instead an expected 30 seconds wait expected [true] but found [false]
  3. 0

    https://github.com/joaquincasares/java-driver/commit/a2a3f8890fc32ce4009c7889c90f34eccee48c14 This is unlike the issues that we've had before. Since the last issue was patched everything was working fine, aside from the race conditions that would last at most a few seconds. This new issue is that the waitFor* code can take as long as 250+ seconds before a node comes online. A 200 second delay handled a large number of cases, yet a 250 second delay handles all but typically 1 or 2. This also impacts the overall time it takes for tests to complete. The following issues tend to occur within the Reconnection and Retry Policy tests due to this new increase as well: {CODE} constantReconnectionPolicyTest(com.datastax.driver.core.ReconnectionPolicyTest) Time elapsed: 78.054 sec <<< FAILURE! java.lang.AssertionError: Waited 70 seconds instead an expected 40 seconds wait expected [true] but found [false] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertTrue(Assert.java:42) at com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:161) at com.datastax.driver.core.ReconnectionPolicyTest.constantReconnectionPolicyTest(ReconnectionPolicyTest.java:119) exponentialReconnectionPolicyTest(com.datastax.driver.core.ReconnectionPolicyTest) Time elapsed: 70.081 sec <<< FAILURE! java.lang.AssertionError: Waited 62 seconds instead an expected 30 seconds wait expected [true] but found [false] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertTrue(Assert.java:42) at com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:161) at com.datastax.driver.core.ReconnectionPolicyTest.exponentialReconnectionPolicyTest(ReconnectionPolicyTest.java:82) defaultLoggingPolicy(com.datastax.driver.core.RetryPolicyTest) Time elapsed: 430.156 sec <<< FAILURE! java.lang.IllegalStateException: 127.0.1.2 is not DOWN after 250s at com.datastax.driver.core.TestUtils.waitFor(TestUtils.java:337) at com.datastax.driver.core.TestUtils.waitForDownWithWait(TestUtils.java:275) at com.datastax.driver.core.RetryPolicyTest.defaultPolicyTest(RetryPolicyTest.java:219) at com.datastax.driver.core.RetryPolicyTest.defaultLoggingPolicy(RetryPolicyTest.java:76) {CODE}

    DataStax JIRA | 3 years ago | Joaquin Casares
    java.lang.AssertionError: Waited 62 seconds instead an expected 30 seconds wait expected [true] but found [false]
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    https://github.com/joaquincasares/java-driver/commit/a2a3f8890fc32ce4009c7889c90f34eccee48c14 This is unlike the issues that we've had before. Since the last issue was patched everything was working fine, aside from the race conditions that would last at most a few seconds. This new issue is that the waitFor* code can take as long as 250+ seconds before a node comes online. A 200 second delay handled a large number of cases, yet a 250 second delay handles all but typically 1 or 2. This also impacts the overall time it takes for tests to complete. The following issues tend to occur within the Reconnection and Retry Policy tests due to this new increase as well: {CODE} constantReconnectionPolicyTest(com.datastax.driver.core.ReconnectionPolicyTest) Time elapsed: 78.054 sec <<< FAILURE! java.lang.AssertionError: Waited 70 seconds instead an expected 40 seconds wait expected [true] but found [false] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertTrue(Assert.java:42) at com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:161) at com.datastax.driver.core.ReconnectionPolicyTest.constantReconnectionPolicyTest(ReconnectionPolicyTest.java:119) exponentialReconnectionPolicyTest(com.datastax.driver.core.ReconnectionPolicyTest) Time elapsed: 70.081 sec <<< FAILURE! java.lang.AssertionError: Waited 62 seconds instead an expected 30 seconds wait expected [true] but found [false] at org.testng.Assert.fail(Assert.java:94) at org.testng.Assert.failNotEquals(Assert.java:494) at org.testng.Assert.assertTrue(Assert.java:42) at com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:161) at com.datastax.driver.core.ReconnectionPolicyTest.exponentialReconnectionPolicyTest(ReconnectionPolicyTest.java:82) defaultLoggingPolicy(com.datastax.driver.core.RetryPolicyTest) Time elapsed: 430.156 sec <<< FAILURE! java.lang.IllegalStateException: 127.0.1.2 is not DOWN after 250s at com.datastax.driver.core.TestUtils.waitFor(TestUtils.java:337) at com.datastax.driver.core.TestUtils.waitForDownWithWait(TestUtils.java:275) at com.datastax.driver.core.RetryPolicyTest.defaultPolicyTest(RetryPolicyTest.java:219) at com.datastax.driver.core.RetryPolicyTest.defaultLoggingPolicy(RetryPolicyTest.java:76) {CODE}

    DataStax JIRA | 3 years ago | Joaquin Casares
    java.lang.AssertionError: Waited 62 seconds instead an expected 30 seconds wait expected [true] but found [false]
  6. 0

    Unit test verifying Message Directory structure fails on Windows 8

    GitHub | 3 years ago | markusgud
    java.lang.AssertionError: U:\tmp\9908_976098897\AP_1000006\9908_81001709 != 9908_976098897/AP_1000006/9908_81001709 expected [true] but found [false]

    6 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.AssertionError

      Waited 32 seconds instead an expected 30 seconds wait expected [true] but found [false]

      at org.testng.Assert.fail()
    2. TestNG
      Assert.assertTrue
      1. org.testng.Assert.fail(Assert.java:94)
      2. org.testng.Assert.failNotEquals(Assert.java:494)
      3. org.testng.Assert.assertTrue(Assert.java:42)
      3 frames
    3. DataStax Java Driver for Apache Cassandra - Core
      ReconnectionPolicyTest.exponentialReconnectionPolicyTest
      1. com.datastax.driver.core.ReconnectionPolicyTest.reconnectionPolicyTest(ReconnectionPolicyTest.java:202)
      2. com.datastax.driver.core.ReconnectionPolicyTest.exponentialReconnectionPolicyTest(ReconnectionPolicyTest.java:82)
      2 frames