Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

add horizontal scaling guide

See original GitHub issue

Hi. I’ve tried to scale Hasura GraphQL Engine deployed to Kubernetes and got various errors after creating tables:

"error":"table \"users\" does not exist","code":"not-exists"

It seems like Hasura is not stateless and caching data into memory. Maybe we need to use something like Redis for a cache.

Issue Analytics

State:
Created 5 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

7reactions

shahidhkcommented, Feb 12, 2019

When #1574 (PR for #1182) is merged, schema can be updated on any one of the hasura instances and others will refresh the metadata automatically.

7reactions

0x777commented, Oct 30, 2018

Hi @Maxpain177 currently modifying schema when you are running several instances of graphql-engine will result in errors like you have seen.

To change schema:

Scale down graphql-engine to 1
Apply all the schema changes
Scale it back to any number

This practice works really well, in development you rarely need to run more than one instance of graphql-engine so you can make changes to the schema, and to deploy the changes to production (which is running many instances of graphql-engine), you’ll just need to wrap the hasura migration apply between two kubectl commands.

We’ll document this

Top Results From Across the Web

Horizontal Scaling | Virtuozzo Dev Docs

The process of manual scaling is fairly simple - open the environment topology wizard and use the appropriate “+” and “-” buttons or...

Horizontal Pod Autoscaling | Kubernetes

Horizontal scaling means that the response to increased load is to deploy more Pods. This is different from vertical scaling, ...

How To Scale MongoDB

Scaling MongoDB horizontally is achieved through sharding (preferred) and replica sets. Sharding Versus Replica Sets. Sharding. horizontal scaling with sharding ...

Manage cluster horizontal scaling (scale out) in Azure Data ...

This article describes steps to scale out and scale in an Azure Data Explorer cluster based on changing demand.

Horizontal scaling implementation

Each host in a horizontal scaling implementation can also support a vertical scaling implementation with the addition of the appropriate servlet implementation ...