Tigris Regions and x-tigris-regions header
Hey!
I have both a request and a question about Tigris regions.
The regions page for Tigris mentions Tigris is deployed in Singapore. I have a server in Singapore which debug.fly.dev shows hitting SIN:
However, in the Grafana Metrics Panel for Tigris I don’t see any requests hitting the
Secondly, I forced my object to be in all regions via the
Sometimes without
Sometimes with
Sometimes
What’s with that, and what does
Thanks for your help!
I have both a request and a question about Tigris regions.
The regions page for Tigris mentions Tigris is deployed in Singapore. I have a server in Singapore which debug.fly.dev shows hitting SIN:
However, in the Grafana Metrics Panel for Tigris I don’t see any requests hitting the
sinsin location. It would be really nice if there was more information exposed in Tigris’s response headers (edge location hit, storage location retrieved from) for debugging. Based on the latency (~250 ms) even after a few requests to a 10 KB object, I assume I’m going somewhere else. I do ~1‑2 ms when ICMP pinging the Tigris endpoint directly.Secondly, I forced my object to be in all regions via the
x-tigris-regionsx-tigris-regions header, and I see some curious information being returned sometimes:Sometimes without
sinsin?Sometimes with
_mr_mr?Sometimes
sinsin comes back?What’s with that, and what does
_mr_mr mean?Thanks for your help!
Solution
Hey, thanks for reporting this. We will debug what’s going on with the requests to your bucket in the SIN region.
Regarding the
Regarding the
*_mr*_mr value reported in the x-tigris-regionsx-tigris-regions header, that is something internal and should not have been reported in the header value. We will fix that.
