You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 13, 2019. It is now read-only.
Our design generally allows easy backups. Necessary steps for this are:
Disable compactor temporarily
Create a backup directory that hard-links to all existing block files
Snapshot() method that allows compacting current in-memory blocks into fully persistent blocks (not strictly necessary but nicer than backing up write-ahead log segments)
Re-enable compactor so we don't ramp up memory during 5. – because all compaction actions replace old files rather than modifying, the inodes the hard links point to remain valid
An external tool, e.g. rsync, can copy the backup directory somewhere safely and delete the directory
To disable/enable the compactor and trigger snapshots we can simply rely on the using application to make the method accessible or provide an optional convenience HTTP server in the tsdb directly.
The text was updated successfully, but these errors were encountered:
Our design generally allows easy backups. Necessary steps for this are:
To disable/enable the compactor and trigger snapshots we can simply rely on the using application to make the method accessible or provide an optional convenience HTTP server in the tsdb directly.
The text was updated successfully, but these errors were encountered: