Repository navigation
feature: HASURA_REPLICAS runs more than one Hasura - #706
Merged
Merged
Conversation
…odes labelled for it
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HASURA_REPLICASin.5stack-env.config(default 1) sets how many Hasuras serve the api.write_overlaysadds a kustomizereplicasentry for the deployment, and rejects anything but a whole number. A preferred pod anti-affinity puts replicas on separate nodes where several are labelled5stack-hasura=true; with one replica it changes nothing.Why: in the api's load lab one Hasura (
-N4) is busy from about 3,000 users. At 3k, a second replica took subscription first data from 3.6 s to 1.4 s (median) and queries from 598 to 233 ms. The cost is Postgres memory: each replica keeps its own pool (pool_settings.max_connections: 16in the api's metadata) plus a few connections of its own, about 1.5 GB more at that load.Don't set it above 1 until api#929 is in the api image: it makes the Hasura pods' init containers take turns running migrations instead of running them at once.