Can't connect to redis instance

Questions / Help
1

We can’t reach our redis instance from any of our apps deployed within the same organization (via the .internal dns). This is luckily only happening on our staging environment atm. luckily (*-redis-staging app name), but it’s only the latest of a series of stability / networking / etc. issues we’ve seen (both in staging and production) over the past few weeks. It’s worrying.

1 Like
2 
Connecting to xxx:xxx:xxx:xxx:xxx:xxxxx:xxx:2... complete
/ # ping top2.nearest.of.xxx-redis-staging.internal
PING top2.nearest.of.xxx-redis-staging.internal (fdaa:0:xxx:xxx:xxx:xxx:xxx:2): 56 data bytes
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=48 ttl=62 time=2220.192 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=49 ttl=62 time=1219.577 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=50 ttl=62 time=217.157 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=51 ttl=62 time=1.314 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=52 ttl=62 time=1.254 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=53 ttl=62 time=56841.463 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=54 ttl=62 time=55841.328 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=55 ttl=62 time=54841.200 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=56 ttl=62 time=53841.056 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=57 ttl=62 time=52840.734 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=58 ttl=62 time=51840.584 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=59 ttl=62 time=50840.439 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=60 ttl=62 time=49840.309 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=61 ttl=62 time=48840.135 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=62 ttl=62 time=47839.954 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=63 ttl=62 time=47987.551 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=64 ttl=62 time=50463.178 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=65 ttl=62 time=50264.810 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=66 ttl=62 time=49264.683 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=67 ttl=62 time=48264.531 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=68 ttl=62 time=47264.375 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=69 ttl=62 time=46264.190 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=70 ttl=62 time=45264.017 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=71 ttl=62 time=44263.839 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=72 ttl=62 time=43263.697 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=73 ttl=62 time=42263.552 ms
64 bytes from xxx:xxx:xxx:xxx:xxx:xxx:xxx:2: seq=74 ttl=62 time=41263.407 ms
3

The host your instance was on suffered high load issues. We’ve been tweaking various settings to prevent this from happening but we’ve had to restart this host in the meantime.

During the high load period, everything was sloggish and that’s probably why pings were so high.