You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We observe that each Hasura instance holds open a connection to the metadata DB for its entire life.
What is the expected behaviour?
It should only hold open a connection when it needs to, e.g. on startup, it should open a connection, read the metadata, and then close the connection. Same thing for exporting / importing / reloading metadata.
How to reproduce the issue?
N/A
Screenshots or Screencast
Please provide any traces or logs that could help here.
Any possible solutions/workarounds you're aware of?
Keywords
The text was updated successfully, but these errors were encountered:
This is due to a metadata sync mechanism among all the instances.
When there are multiple instances running, metadata can be modified by any instance. Each hasura instance keeps a connection open so it can detect if there's a new version of the metadata, and then refresh it.
In my experience the Hasura instances only reload metadata from the DB when you send a reload_metadata request via the metadata API. From looking at the docs I can't find a reference to this behavior or any way to configure it (e.g. the frequency), could you point that out?
Version Information
Server Version: 2.40.2-ce
Environment
OSS
What is the current behaviour?
We observe that each Hasura instance holds open a connection to the metadata DB for its entire life.
What is the expected behaviour?
It should only hold open a connection when it needs to, e.g. on startup, it should open a connection, read the metadata, and then close the connection. Same thing for exporting / importing / reloading metadata.
How to reproduce the issue?
N/A
Screenshots or Screencast
Please provide any traces or logs that could help here.
Any possible solutions/workarounds you're aware of?
Keywords
The text was updated successfully, but these errors were encountered: