sudden spike in egress usage

Hey, since I migrated my DB to v2, my egress has shot up. I want to know if these are related and also what is causing the crazy spike in egress. 26479513-66db-4cef-b0ea-47a942afad95
19 Replies
Percy
Percy11mo ago
Project ID: 26479513-66db-4cef-b0ea-47a942afad95
Brody
Brody11mo ago
are you using the private urls?
croissant
croissant11mo ago
No i'm using viaduct. I tried moving to private_url and my build kept crashing because DB was unreachable Am i missing some config?
Brody
Brody11mo ago
viaduct is the public url so that's likely why you are seeing egress usage, and the private network is not available during build so you would need to do the database migrations during runtime before your app starts I'm only assuming migrations are what you are doing
croissant
croissant11mo ago
My bad, it's not build. The app kept crashing i changed the URL to private again just now
croissant
croissant11mo ago
No description
Brody
Brody11mo ago
ioredis?
croissant
croissant11mo ago
node-redis Works just fine on public URL
Brody
Brody11mo ago
what version of node-redis?
croissant
croissant11mo ago
4.6.8
croissant
croissant11mo ago
GitHub
GitHub - arhammusheer/croissant-home-apis
Contribute to arhammusheer/croissant-home-apis development by creating an account on GitHub.
croissant
croissant11mo ago
it's not private code
Brody
Brody11mo ago
when was 4.6.8 released?
croissant
croissant11mo ago
seems like 4 months ago I can try upgrading
Brody
Brody11mo ago
4 months ago should be new enough to support ipv6
croissant
croissant11mo ago
from the error it seems like it's not able to resolve internal domain
Brody
Brody11mo ago
can you try to add a 3 second sleep to your start command?
croissant
croissant11mo ago
Don't think it'll help. Redis connection is opened on request and closed frequently
Brody
Brody11mo ago
ah then try upgrading
Want results from more Discord servers?
Add your server