labels.zone set to tiproxy instance fail when balance policy= 'location'
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
create premium cluster with tiproxy config:
[balance]
label-name = "keyspace"
policy = "location"
2. What did you expect to see? (Required)
check tiproxy labels in logs, zone label and value should included in the [labels] structure.
3. What did you see instead (Required)
no "zone" in the [labels] structure.
4. What is your version? (Required)
premium cluster
version: v26.3.99
tag: v26.3.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the premium cluster configuration with [balance] label-name = "keyspace" and policy = "location" on v26.3.99. Trace how the tiproxy instance builds its [labels] structure and compare the location-policy path with other balance policies. Done means the zone label and value appear in logs for this configuration, with a regression test if the relevant test location is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100