AWS Hasura becomes unresponsive, then ok again for a while! #9181
Unanswered
paulfentonfuse
asked this question in
Question
Replies: 1 comment 5 replies
-
Hey @paulfentonfuse Can we know which edition of hasura you are using ? Is it open source (community edition) or enterprise edition (EE) ? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have launched an instance of container definition hasura/graphql-engine:v2.14.0 to AWS as a FARGATE ECS service with one task and resources CPU 256 and memory 1024. It is connected to a RDS postgres database within AWS.
I can successfully connect to the Hasura console and my schema is perfect for my database.
However, every few minutes, both the console and external graphql interfacing becomes unresponsive. In the console, the red progress bar at the top hovers at around 95% and then suddenly completes after about 60-90 secs.
Hasura will then operate normally for a few minutes and then the whole thing repeats!
I have other Hasura instances of the same spec that work perfectly fine, but this one is problematic.
I have searched the RDS instance logs, ECS container logs and nothing appears to be generating any errors.
Has anyone else experienced this and what else can I look for?? Appreciated in advance!
Beta Was this translation helpful? Give feedback.
All reactions