Repository navigation
Statement-timeout 503s, read-only scope restore, read-model restore logs - #40
Merged
Merged
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
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.
Docs for MeshCore-Beacon/beacon-server#264.
503deadline_exceededwithRetry-After: 10on route evidence and the background-data pages; other endpoints still answer500. Route evidence row notes it.meshmapper.scopes.enabled, a read-only server loads the writer's saved scope catalogues once at boot, so region scope lists match the writer's as of that boot.read model trusted again: …andread model untrusted: repair runs fixed rows the writers missedlog lines for cmi and packet_sites;beacon_api_unavailable_totalreasontimeout.