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
After TS restart, transaction status tablets are fetched before RemoteTabletServer has its placement set, resulting in the initial fetch always only fetching global tablets. No further fetch is done until a change in transaction status tables happens (new transaction status table created/placement set), until which all queries through the restarted TS will always use the global transaction table.
…nto one RPC
Summary:
Consolidates the many RPCs made when the transaction manager updates the
transaction status tablet cache into a single RPC which returns the relevant lists
of global and local transaction status tablet ids. Addresses bug where the initial
fetch of transaction table tablets in TransactionManager does not fetch placement
local tablets.
Test Plan: `ybd --cxx-test pgwrapper_geo_transactions-test`
Reviewers: bogdan, mbautin, sergei
Reviewed By: sergei
Subscribers: ybase
Differential Revision: https://phabricator.dev.yugabyte.com/D13957
…t cache update into one RPC
Summary:
Consolidates the many RPCs made when the transaction manager updates the
transaction status tablet cache into a single RPC which returns the relevant lists
of global and local transaction status tablet ids. Addresses bug where the initial
fetch of transaction table tablets in TransactionManager does not fetch placement
local tablets.
Original Commit: D13957 / 0c05d05
Test Plan:
Jenkins: rebase 2.12, urgent
`ybd --cxx-test pgwrapper_geo_transactions-test`
Reviewers: bogdan, mbautin, sergei
Subscribers: ybase
Differential Revision: https://phabricator.dev.yugabyte.com/D15196
Description
After TS restart, transaction status tablets are fetched before RemoteTabletServer has its placement set, resulting in the initial fetch always only fetching global tablets. No further fetch is done until a change in transaction status tables happens (new transaction status table created/placement set), until which all queries through the restarted TS will always use the global transaction table.
Context: #10158, #9980
The text was updated successfully, but these errors were encountered: