You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Andrew Wong (JIRA)" <ji...@apache.org> on 2019/02/20 00:45:00 UTC
[jira] [Commented] (KUDU-2703) ITClientStress.testMultipleSessions
timeout
[ https://issues.apache.org/jira/browse/KUDU-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772480#comment-16772480 ]
Andrew Wong commented on KUDU-2703:
-----------------------------------
Haven't looked very deeply at this, but, looking at a successful run (test-output.txt), I see those messages too. !test-output.txt|width=7,height=7,align=absmiddle!
That said, the safe time difference posted seems to be larger than the few in the successful case that I looked at (e.g. 2e8 to 1e9 in the successful log vs 4e9 in this snippet).
> ITClientStress.testMultipleSessions timeout
> -------------------------------------------
>
> Key: KUDU-2703
> URL: https://issues.apache.org/jira/browse/KUDU-2703
> Project: Kudu
> Issue Type: Test
> Reporter: Hao Hao
> 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
(v7.6.3#76005)