This repository was archived by the owner on Mar 7, 2018. It is now read-only.
Block server start until Cassandra is initialized #98
Conversation
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
c-w
force-pushed
the
server-start-blocker
branch
from
e7af6e8 to
881249b
Compare
The first request to Cassandra is very slow (on the order of 20 seconds during my testing), I reckon because the connection and pool are being built up. Subsequent requests are much faster (sub-second). We don't want our users to have a problem with hitting the slow first request, so we should warm up the Cassandra connection before we let the server start. In this way, when we re-deploy the GraphQL server, we'll simply continue running the instances of the old code in the load balancer until the new server is fully operational and has warmed up the Cassandra connection.
c-w
force-pushed
the
server-start-blocker
branch
from
6be9184 to
c595ac0
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The first request to Cassandra is very slow (on the order of 20 seconds
during my testing), I reckon because the connection and pool are being
built up. Subsequent requests are much faster (sub-second).
We don't want our users to have a problem with hitting the slow first
request, so we should warm up the Cassandra connection before we let the
server start. In this way, when we re-deploy the GraphQL server, we'll
simply continue running the instances of the old code in the load
balancer until the new server is fully operational and has warmed up the
Cassandra connection.