Bug #98389 Contribution by Facebook: update perfschema.idx_compare_replication_applier ...
Submitted: 25 Jan 2020 18:17 Modified: 4 Mar 2020 19:40
Reporter: FBContrib Admin Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Tests Severity:S3 (Non-critical)
Version:8.0.17 OS:Any
Assigned to: CPU Architecture:Any

[25 Jan 2020 18:17] FBContrib Admin
Background innformation provided by Facebook:
update the testcase to save the old value(before testcase run) first, and compare with the new value(after the testcase run) with the old value.

Use case:

Some of our test cases causes transaction retries, so the value is non-zero when this test runs. Changing the test to calculate the difference fixes this issue.

Repo: https://github.com/mysql/mysql-server

Patch on top of 8.0.17: https://github.com/mysql/mysql-server/commit/4869291f7ee

How to repeat:
See description

Suggested fix:
See contribution code attached
[25 Jan 2020 18:17] FBContrib Admin
update perfschema.idx_compare_replication_applier_status to be more robust 
(*) This code is contributed under the Facebook agreement

Contribution: fb_patch_175.txt (text/plain), 2.17 KiB.

[4 Mar 2020 19:40] Paul DuBois
Posted by developer:
Fixed in 8.0.20.

The perfschema.idx_compare_replication_applier_status test case was
updated to store the old value of number of transaction retries and
compare it with the new value of number of transaction retries.
Thanks to Facebook for the contribution.
[23 Mar 2020 20:20] Omer Barnir
Thanks to Facebook for the contribution