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
[#28761] DocDB: Prevent requesting new txn when releasing object locks on finish if txn doesn't exist
Summary:
`NextObjectLockingTxnMeta` returns transaction if one exists, else creates a new one and waits in-line. This is used for acquiring/releasing object locks when a distributed docdb transaction doesn't exist.
It could happen that we receive redundant finish transaction calls, and try releasing object locks when both docdb transaction and `next_plain_` don't exist. In that case, the release would request a new transaction, which isn't necessary.
The above causes some tests to fail because of the clean shutdown semantics enforced in [[ https://phorge.dev.yugabyte.com/D46293 | commit ]]. This diff fixes the issue by not requesting a new transaction for release/finish calls.
Jira: DB-18473
Test Plan:
Jenkins
Enabled object locking and ran the following
```
PgAutoAnalyzeTest_CheckTableMutationsCount
PgCatalogPerfTest.CacheRefreshRPCCountWithoutPartitionTables
```
Also triggered a jenkins run with table locks enabled and the changes in this revision, some failures in https://phorge.dev.yugabyte.com/D44416 are resolved.
Reviewers: rthallam, amitanand
Reviewed By: amitanand
Subscribers: yql, ybase
Differential Revision: https://phorge.dev.yugabyte.com/D47342
0 commit comments