Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: select @@vtgate_hostname; support #17272

Open
serhatcetinkaya opened this issue Nov 22, 2024 · 0 comments
Open

Feature Request: select @@vtgate_hostname; support #17272

serhatcetinkaya opened this issue Nov 22, 2024 · 0 comments
Labels
Needs Triage This issue needs to be correctly labelled and triaged

Comments

@serhatcetinkaya
Copy link

serhatcetinkaya commented Nov 22, 2024

Feature Description

Hello, I previously opened #17246 and continued discussion with @harshit-gangal in the community slack. The common decision was to create a feature request for it.

This is a feature request to have some mechanism to run select @@vtgate_hostname; or select @@vtgate_id; from the client and retrieving hostname/host id of the vtgate on the other end of the connection.

Use Case(s)

For the following use case on our side this would be very helpful and save us hours of debugging:

We have our application deployed in 3 different AZ's, similarly vtgate is also deployed in 3 different AZ's and application creates connection to vtgate over a layer 4 load balancer. Rarely we see increased database latency metrics on subset of the application instances. After hours of debugging we figured out requests from one specific AZ to another one had an intermittent issue on cloud provider side and this was the reason. If we'd known which application instance is connected to which vtgate in advance, we could have quickly notice the latency pattern.

@serhatcetinkaya serhatcetinkaya added the Needs Triage This issue needs to be correctly labelled and triaged label Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Triage This issue needs to be correctly labelled and triaged
Projects
None yet
Development

No branches or pull requests

1 participant