prometheus/storage/remote
Tom Wilkie efbd9559f4 Deal with corruptions in the WAL:
- If we're replaying the WAL to get series records, skip that segment when we hit corruptions.
- If we're tailing the WAL for samples, fail the watcher.
- When the watcher fails, restart from the latest checkpoint - and only send new samples by updating startTime.
- Tidy up log lines and error handling, don't return so many errors on quiting.
- Expect EOF when processing checkpoints.

Signed-off-by: Tom Wilkie <tom.wilkie@gmail.com>
2019-02-28 08:38:39 -08:00
..
client.go Tail the TSDB WAL for remote_write 2019-02-12 11:39:13 +00:00
client_test.go Tail the TSDB WAL for remote_write 2019-02-12 11:39:13 +00:00
codec.go Tail the TSDB WAL for remote_write 2019-02-12 11:39:13 +00:00
codec_test.go *: apply gofmt -s 2019-01-16 17:28:14 -05:00
ewma.go Initial port of remote storage to v2. 2017-07-12 12:27:57 +01:00
queue_manager.go Deal with corruptions in the WAL: 2019-02-28 08:38:39 -08:00
queue_manager_test.go Deal with corruptions in the WAL: 2019-02-28 08:38:39 -08:00
read.go Move err to be the last return value from storage.Select. (#5054) 2019-01-02 11:10:13 +00:00
read_test.go Move err to be the last return value from storage.Select. (#5054) 2019-01-02 11:10:13 +00:00
storage.go Deal with corruptions in the WAL: 2019-02-28 08:38:39 -08:00
wal_watcher.go Deal with corruptions in the WAL: 2019-02-28 08:38:39 -08:00
wal_watcher_test.go Deal with corruptions in the WAL: 2019-02-28 08:38:39 -08:00
write.go Export timestamps in seconds since epoch. 2019-02-28 08:38:39 -08:00