Skip to main content

heroku-and-redis-physical-region

Heroku (POWr Prod Server)​

=== powr
Dynos:          web: 45, worker: 15, scheduler: 2
Git URL:        https://git.heroku.com/powr.git
Owner:          [email protected]
Region:         us
Repo Size:      528 MB
Slug Size:      463 MB
Stack:          container
Web URL:        https://powr.herokuapp.com/

Details​


curl -n -X GET https://api.heroku.com/regions/us -H "Accept: application/vnd.heroku+json; version=3"
{
  "country":"United States",
  "created_at":"2012-11-21T20:44:16Z",
  "description":"United States",
  "id":"59accabd-516d-4f0e-83e6-6e3757701145",
  "locale":"Virginia",
  "name":"us",
  "private_capable":false,
  "provider":{
    "name":"amazon-web-services",
    "region":"us-east-1"
  },
  "updated_at":"2016-08-09T22:03:28Z"
}

Compose (POWr Prod Redis)​

Screen Shot 2020-07-21 at 5.01.11 PM.png

Conclusion, they are both hosted on same region. During last staging’s redis shit show, I had created a redis instance on us-west-2 for staging to use, that did not go very well, as staging, and powr-review app crashed a lot. When we created another instance on us-east-1 again, it magically worked. Which means, the regions we currently using is us-east-1 and is the correct region we should be using, when/if we have to restore again, we should always make sure to restore on us-east-1 region.