You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[#29343] YSQL: Make sure each batch has enough of PgsqlOps
Summary:
We could not reproduce the issue reported by #29343 in a controlled
environment, however after core dump analysis we figured out that while
making batches to fetch data from the base table by ybctids the
PgDocReadOp instance did not have sufficient number PgsqlOps/ReadReqs.
There was one PgsqlOp/ReadReq while the table had 2 tablets.
In 8fa242d where the issue was
allegedly introduced we changed the logic of PgsqlOps/ReadReqs
repopulation after cleanup between the batches. We create as many
PgsqlOps/ReadReqs as there were in the previous batch, assuming that the
number of the PgsqlOps/ReadReqs needed does not change between the
batches. Apparently that assumption was incorrect, so here we
recalculate the number for each batch and make sure we have that number
of the PgsqlOps/ReadReqs created.
Test Plan:
Make sure there is no regression in Jenkins
Since the issue was only reproduced in perf environment, rerun perf tests on the diff
Reviewers: jason
Reviewed By: jason
Subscribers: yql
Tags: #jenkins-ready
Differential Revision: https://phorge.dev.yugabyte.com/D48246
0 commit comments