[
https://issues.apache.org/jira/browse/KUDU-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988323#comment-16988323
]
ASF subversion and git services commented on KUDU-2703:
-------------------------------------------------------
Commit 89ce529e945731c48445db4a6f8af11f9f905aab in kudu's branch
refs/heads/master from Adar Dembo
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=89ce529 ]
KUDU-2703: deflake ITClientStress timeouts
These tests have been timing out in TSAN fairly consistently. I see no
reason why we can't increase the timeouts.
org.junit.runners.model.TestTimedOutException: test timed out after 60000
milliseconds
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at com.stumbleupon.async.Deferred.doJoin(Deferred.java:1136)
at com.stumbleupon.async.Deferred.join(Deferred.java:1019)
at org.apache.kudu.client.KuduSession.apply(KuduSession.java:81)
at
org.apache.kudu.client.ITClientStress$3$1.call(ITClientStress.java:164)
at
org.apache.kudu.client.ITClientStress$3$1.call(ITClientStress.java:151)
at org.apache.kudu.client.ITClientStress$1.run(ITClientStress.java:81)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy.rejectedExecution(ThreadPoolExecutor.java:2038)
at
java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
at
java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112)
at
org.apache.kudu.client.ITClientStress.runTasks(ITClientStress.java:87)
at
org.apache.kudu.client.ITClientStress.testMultipleSessions(ITClientStress.java:148)
Change-Id: I3f5f1713be093c3116743c4a72f30f2f6262974e
Reviewed-on: http://gerrit.cloudera.org:8080/14838
Reviewed-by: Alexey Serbin <[email protected]>
Tested-by: Kudu Jenkins
> ITClientStress.testMultipleSessions timeout
> -------------------------------------------
>
> Key: KUDU-2703
> URL: https://issues.apache.org/jira/browse/KUDU-2703
> Project: Kudu
> Issue Type: Test
> Reporter: Hao Hao
> Assignee: Adar Dembo
> Priority: Major
> Attachments: TEST-org.apache.kudu.client.ITClientStress.xml,
> test-output.txt
>
>
> I recently encountered a timeout of ITClientStress.testMultipleSessions with
> the following errors:
> {noformat}
> 01:28:10.477 [INFO - cluster stderr printer] (MiniKuduCluster.java:543) I0219
> 01:28:10.477150 7258 mvcc.cc:203] Tried to move safe_time back from
> 6351128536717332480 to 6351128535804997632. Current Snapshot:
> MvccSnapshot[committed={T|T < 6351128536717332480}]
> 01:28:10.495 [INFO - cluster stderr printer] (MiniKuduCluster.java:543) I0219
> 01:28:10.495507 7259 mvcc.cc:203] Tried to move safe_time back from
> 6351128536717332480 to 6351128535804997632. Current Snapshot:
> MvccSnapshot[committed={T|T < 6351128536717332480}]
> 01:28:11.180 [INFO - cluster stderr printer] (MiniKuduCluster.java:543) I0219
> 01:28:11.180346 7257 mvcc.cc:203] Tried to move safe_time back from
> 6351128539811692544 to 6351128535804997632. Current Snapshot:
> MvccSnapshot[committed={T|T < 6351128539811692544 or (T in
> {6351128539811692544})}]
> 01:28:19.969 [DEBUG - New I/O worker #2152] (Connection.java:429) [peer
> master-127.6.95.253:51702(127.6.95.253:51702)] encountered a read timeout;
> closing the channel
> 01:28:19.969 [DEBUG - New I/O worker #2154] (Connection.java:429) [peer
> master-127.6.95.254:34354(127.6.95.254:34354)] encountered a read timeout;
> closing the channel
> 01:28:19.969 [DEBUG - New I/O worker #2154] (Connection.java:688) [peer
> master-127.6.95.254:34354(127.6.95.254:34354)] cleaning up while in state
> READY due to: [peer master-127.6.95.254:34354(127.6.95.254:34354)]
> encountered a read timeout; closing the channel
> 01:28:19.969 [DEBUG - New I/O worker #2152] (Connection.java:688) [peer
> master-127.6.95.253:51702(127.6.95.253:51702)] cleaning up while in state
> READY due to: [peer master-127.6.95.253:51702(127.6.95.253:51702)]
> encountered a read timeout; closing the channel
> 01:28:20.328 [DEBUG - New I/O worker #2153] (Connection.java:429) [peer
> master-127.6.95.252:47527(127.6.95.252:47527)] encountered a read timeout;
> closing the channel
> {noformat}
> Looking at the error, it may relate to safe time advancement. Attached the
> full log.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
