Investigate if UserFateStore should also be used where MetaFateStore is
kevinrr888 opened this issue · 3 comments
Is your feature request related to a problem? Please describe.
In elasticity, the transaction store (ZooStore) was split into two stores: a new store for user transactions (UserFateStore) in addition to the existing MetaFateStore (ZooStore in 2.1/main). From this change, there are places where MetaFateStore is still the only store used where UserFateStore should be used as well.
Describe the solution you'd like
It should be investigated where MetaFateStore is used if UserFateStore should also be used
Additional context
This is for elasticity
Looking into this
- #4534 is one issue already opened related to this
-
UpgradeCoordinator.abortIfFateTransactions()
is another place where UFS should also be used -
FunctionalTestUtils.getFateStatus()
should use both
Everywhere else where MetaFateStore
is used either correctly only uses MetaFateStore
or correctly uses both: FateConcurrencyIT
, ExternalCompaction_1_IT
, MetaFateStoreFateIT
, MetaFateIT
, MetaFateOpsCommandsIT
, MetaFateInterleavingIT
, Manager
, Admin
, AdminUtil
This issue can be closed: #4696
While one of the above is not complete, that has it's own issue for it