Check for scribe needing to be restarted due to low memory #122
No reviewers
Labels
No labels
area: database
area: documentation
area: elasticsearch
area: herald
area: packaging
area: scribe
consider soon
critical
dependencies
good first issue
hacktoberfest
help wanted
improvement
needs: repro
new feature
priority: blocker
priority: high
priority: low
priority: medium
type: bug
type: bug-fix
type: discussion
type: feature request
type: improvement
type: new feature
type: refactor
type: task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/hub#122
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "remove-unused-settings"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This updates scribe to check for a canary file being created when herald or es-sync fail to open the db and to shut down in order to be restarted.
When the primary db hasn't done a compaction flush it can cause the secondary dbs to require much more memory to open than normal until the primary is cycled. When memory is low this can cause herald/es-sync to get stuck in a restart loop until scribe is restarted.