-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[#17940] DocDB: Include node information in pg_locks output
Summary: `GetLockStatus` in pg_client_service.cc returns lock info of either old transactions (older than `min_txn_age`) or the specified transaction set. For the former case, this diff augments the response by including host node uuid of the involved transactions whose lock info is being returned. We include the node uuid in the transaction heartbeats sent from the query layer and make the txn coordinator store the host node uuid. We return the host node info from the coordinator when queried for old transactions. The query layer parses this info and populates `PgGetLockStatusResponsePB` resp with host node uuids of involved transactions. When the incoming `PgGetLockStatusRequestPB` contains a transaction id, we directly broadcast get lock status request to all tservers skipping the coordinator. Since we skip the coordinator, we don't get the host node info. This will be addressed as part of #16913 Jira: DB-7013 Test Plan: ./yb_build.sh --cxx-test pgwrapper_pg_get_lock_status-test --gtest_filter PgGetLockStatusTest.TestGetLockStatusOfOldTxns ./yb_build.sh --cxx-test pgwrapper_pg_get_lock_status-test --gtest_filter PgGetLockStatusTest.TestGetLockStatusLimitNumOldTxns Reviewers: rsami Reviewed By: rsami Subscribers: ybase, bogdan Differential Revision: https://phorge.dev.yugabyte.com/D26957
- Loading branch information
1 parent
50123f1
commit 6a79146
Showing
8 changed files
with
57 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters