Repository navigation
Raise the Realtime limits after restarting it - #34
Merged
Merged
Conversation
Realtime reseeds its tenant with the default limits when it starts (SEED_SELF_HOST), so updating the tenant and then restarting put the 100 a second limit straight back. Co-authored-by: Ferrin <177692050+Ferrin-Y@users.noreply.github.com> Co-authored-by: noorelmosrati <182049385+noorelmosrati@users.noreply.github.com>
This branch was successfully deployed
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.
#32 raised the local Realtime tenant's limits and then restarted Realtime. Realtime reseeds its tenant with the defaults when it starts (
SEED_SELF_HOST=true), so the restart put the 100 a second limit straight back, and live update journeys still hitMessagePerSecondRateLimitReached(seen again on #33). The green run after #32 was luck.This restarts Realtime first, waits until it is healthy, then raises the limits before any client connects, and prints the stored value. Checked on a local stack: the tenant reads 1000 after the restart and stays there. docs/testing.md has the same order for local runs.