QueryNode: Run graphql-server with pm2 cluster mode#4863
Merged
mnaamani merged 4 commits intoJoystream:masterfrom Oct 25, 2023
Merged
QueryNode: Run graphql-server with pm2 cluster mode#4863mnaamani merged 4 commits intoJoystream:masterfrom
mnaamani merged 4 commits intoJoystream:masterfrom
Conversation
710993e to
da57d7b
Compare
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.
Enable horizontal scaling graphql-server on machine using pm2 process manager in cluster mode.
The updated script to start graphql-server will only start a single node cluster. Once the graphql-server is running we can manage the cluster with pm2:
Get status:
docker exec -it graphql-server yarn pm2 statusAdd one more instance to the cluster
docker exec -it graphql-server yarn pm2 scale graphql-server +1Monitor the cluster:
docker exec -it graphql-server yarn pm2 statusIts important to note that the processor send status updates to the graphql-server. As more instances are added, these udpates are balanced across the cluster, so they will appear less frequent from the point of view of applications that are subscribing through the graphql-server to these updates.