VTAdmin: Distributed transactions list on VTAdmin

[beingnoble03]

Description

• Includes TimeCreated while querying unresolved transactions
• Adds VTAdmin API endpoint to fetch the transactions by keyspace
• Initiates the Transactions screen on VTAdmin web.

Sample output from API:

{
    "result": {
        "transactions": [
            {
                "dtid": "1",
                "state": 1,
                "participants": [
                    {
                        "keyspace": "commerce",
                        "shard": "0",
                        "tablet_type": 1
                    }
                ]
            },
            {
                "dtid": "2",
                "state": 1,
                "participants": [
                    {
                        "keyspace": "commerce",
                        "shard": "0",
                        "tablet_type": 1
                    }
                ]
            }
        ]
    },
    "ok": true
}

Related Issue(s)

• Feature Request: Distributed Transaction Actions on VTAdmin  #16766

Screenshots

Checklist

• "Backport to:" labels have been added if this change should be back-ported to release branches
• If this change is to be back-ported to previous releases, a justification is included in the PR description
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on CI?
• Documentation was added or is not required

Deployment Notes

[vitess-bot]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

• Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

• Apply the release notes (needs details) label if users need to know about this change.
• New features should be documented.
• There should be some code comments as to why things are implemented the way they are.
• There should be a comment at the top of each new or modified test to explain what the test does.

New flags

• Is this flag really necessary?
• Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
• vtctl command output order should be stable and awk-able.

[codecov]

Codecov Report

Attention: Patch coverage is 20.83333% with 19 lines in your changes missing coverage. Please review.

Project coverage is 69.51%. Comparing base (56c39b2) to head (b1918eb).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
go/vt/vtadmin/api.go	7.69%	12 Missing ⚠️
go/vt/vtadmin/http/transactions.go	0.00%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16793      +/-   ##
==========================================
- Coverage   69.53%   69.51%   -0.02%     
==========================================
  Files        1567     1568       +1     
  Lines      202388   202423      +35     
==========================================
- Hits       140723   140708      -15     
- Misses      61665    61715      +50     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[harshit-gangal]

We should call it In Flight Distributed Transactions on the Transactions page.
Also, we can ignore the tablet type information of the shard as all will be Primary only.

[harshit-gangal]

We should also display the age of the transaction to know from how long the transaction is unresolved.

[harshit-gangal]

When we call for getting unresolved transactions for a keyspace.
There is a request parameter called abandonAge.
We should use that and may be provide options to user to tell how old the transaction should be to display on VTAdmin.
5s, 30s, 5min, etc.

[harshit-gangal]

This can also be done in a follow up PR.