[ 
https://issues.apache.org/jira/browse/KUDU-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640943#comment-17640943
 ] 

ASF subversion and git services commented on KUDU-3425:
-------------------------------------------------------

Commit ed648cf8a2491e78f3d693a8c1be9077ed064864 in kudu's branch 
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=ed648cf8a ]

KUDU-3425 fix flakiness in TestSnapshotScanBeforeAHM

This patch fixes the flakiness in the TestSnapshotScanBeforeAHM scenario
of the TabletHistoryGcITest test.  The root cause was in
IsAlterTableDone() RPC reporting 'all is done' prior the tablet replica
that served the scan request has received the update on the custom
config for the scanned table.

Setting replication factor to 1 from default 3 made the scenario stable.

before: 19 out of 1024 failed
  http://dist-test.cloudera.org/job?job_id=aserbin.1669681704.94942

after:   0 out of 1024 failed
  http://dist-test.cloudera.org/job?job_id=aserbin.1669686405.116123

Change-Id: Ib31e18c2a5ae68d05b4b0b0db15ff1cd00ac240b
Reviewed-on: http://gerrit.cloudera.org:8080/19284
Tested-by: Alexey Serbin <[email protected]>
Reviewed-by: Yifan Zhang <[email protected]>


> TabletHistoryGcITest.TestSnapshotScanBeforeAHM fails intermittently
> -------------------------------------------------------------------
>
>                 Key: KUDU-3425
>                 URL: https://issues.apache.org/jira/browse/KUDU-3425
>             Project: Kudu
>          Issue Type: Bug
>          Components: test
>            Reporter: Alexey Serbin
>            Assignee: Alexey Serbin
>            Priority: Minor
>
> The {{TabletHistoryGcITest.TestSnapshotScanBeforeAHM}} shows signs of 
> flakiness, failing from time to time with errors like below:
> {noformat}
> src/kudu/integration-tests/tablet_history_gc-itest.cc:172
> Failed
> Bad status: Invalid argument: snapshot scan end timestamp is earlier than the 
> ancient history mark. Consider increasing the value of the configuration 
> parameter --tablet_history_max_age_sec. Snapshot timestamp: P: 
> 1669591267778185 usec, L: 0 Ancient History Mark: P: 1669591267778244 usec, 
> L: 0 Physical time difference: -0.000s
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to