PITR restore causing data mismatch in stress test test_ycql_snapshots_splitting

[agsh-yb]

Jira Link: DB-13932

Description

Failed to check consistency
This issue is observed only with connection manager flags

additional_tserver_gflags.enable_ysql_conn_mgr=true, additional_tserver_gflags.allowed_preview_flags_csv=enable_ysql_conn_mgr

Version : 2024.2.0.0-b116

Error:

Expected max_value is different from actual max_value after PITR restore

Diff: {"postgresqlkeyvalue0": "Expected {"count": 956003, "max_key": "ac84eb79-2122-40e0-b01b-9120912d0c87:99999", "min_key": "ac84eb79-2122-40e0-b01b-9120912d0c87:0", "max_val": "ac84eb79-2122-40e0-b01b-9120912d0c87:99999", "min_val": "ac84eb79-2122-40e0-b01b-9120912d0c87:0"}, actual {"count": 956033, "max_key": "f22c8e99-c5e7-4685-8eeb-bb5526f220b7:96", "min_key": "ac84eb79-2122-40e0-b01b-9120912d0c87:0", "max_val": "f22c8e99-c5e7-4685-8eeb-bb5526f220b7:96", "min_val": "ac84eb79-2122-40e0-b01b-9120912d0c87:0"}"}

Stress report in Jira

Issue Type

kind/bug

Warning: Please confirm that this issue does not contain any sensitive information

• I confirm this issue does not contain any sensitive information.