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
We currently calculate a transaction table version hash over transaction table ids and schema versions to indicate to tservers that a change in transaction tables has occurred and that a refresh of the transaction tablet cache is needed, but in the event of a hash collision, we end up not refreshing the cache. This should be changed to use a version number maintained by the master to ensure all changes are always followed by a cache refresh.
The text was updated successfully, but these errors were encountered:
…es to transaction tables
Summary:
Replaced transaction status version hash + TS-local transaction status versions with
a single global transaction tables version maintained by master, to remove the possibility of
hash conflicts resulting in tablet servers not updating the transaction status tablet cache when
needed.
Depends on D14255
Test Plan: `ybd --cxx-test pgwrapper_geo_transactions-test`
Reviewers: bogdan, sergei
Reviewed By: sergei
Subscribers: ybase
Differential Revision: https://phabricator.dev.yugabyte.com/D15388
…ng updates to transaction tables
Summary:
Replaced transaction status version hash + TS-local transaction status versions with
a single global transaction tables version maintained by master, to remove the possibility of
hash conflicts resulting in tablet servers not updating the transaction status tablet cache when
needed.
Depends on D14255
Test Plan: `ybd --cxx-test pgwrapper_geo_transactions-test`
Reviewers: bogdan, sergei
Reviewed By: sergei
Subscribers: ybase
Differential Revision: https://phabricator.dev.yugabyte.com/D15388
Description
Context: #9980
We currently calculate a transaction table version hash over transaction table ids and schema versions to indicate to tservers that a change in transaction tables has occurred and that a refresh of the transaction tablet cache is needed, but in the event of a hash collision, we end up not refreshing the cache. This should be changed to use a version number maintained by the master to ensure all changes are always followed by a cache refresh.
The text was updated successfully, but these errors were encountered: