RepoMirrors
/
prometheus
mirror of https://github.com/prometheus/prometheus
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
prometheus/CHANGELOG.md

16 lines
1.2 KiB
Markdown
Raw Normal View History

refactor NewSegmentsRangeReader to take multi WAL ranges (#449) * refactor NewSegmentsRangeReader to take multi WAL ranges In case of an error when checkpointing the WAL the error doesn't show the exact WAL index that is corrupter. this is because it uses MultiReader to read multiply WAL files. This refactoring allows the NewSegmentsRangeReader to take more than a single WAL range and it reads all of the ranges by iterating each one. this changes the logs from create checkpoint: read segments: corruption after 4841144384 bytes:... to create checkpoint: read segments: corruption in segment data/wal/00017351 at 123142208: ... Signed-off-by: Krasi Georgiev <kgeorgie@redhat.com>
2018-11-30 14:46:16 +00:00
## master / unreleased
Add WALSegmentSize as an option of tsdb creation (#450) Expose `WALSegmentSize` option to allow overriding the `DefaultOptions.WALSegmentSize`.
2018-12-18 18:56:51 +00:00
- [CHANGE] New `WALSegmentSize` option to override the `DefaultOptions.WALSegmentSize`. Added to allow using smaller wal files. For example using tmpfs on a RPI to minimise the SD card wear out from the constant WAL writes. As part of this change the `DefaultOptions.WALSegmentSize` constant was also exposed.
remove unused WALFlushInterval option and NopWAL struct (#468) The WALFlushInterval is not used anywhere in the code base. The WAL is not an interface anymore to save some lookup time so can't use NopWAL in the tests. Instead can just pass nil as the code checks for that and it is essentially a noop. Signed-off-by: Krasi Georgiev <kgeorgie@redhat.com>
2018-12-28 17:42:46 +00:00
- [CLEANUP] `Options.WALFlushInterval` is removed as it wasn't used anywhere.
release 0.3.1 (#477) Signed-off-by: Krasi Georgiev <kgeorgie@redhat.com>
2018-12-13 14:02:32 +00:00
## 0.3.1
remove unused WALFlushInterval option and NopWAL struct (#468) The WALFlushInterval is not used anywhere in the code base. The WAL is not an interface anymore to save some lookup time so can't use NopWAL in the tests. Instead can just pass nil as the code checks for that and it is essentially a noop. Signed-off-by: Krasi Georgiev <kgeorgie@redhat.com>
2018-12-28 17:42:46 +00:00
- [BUGFIX] Fixed most windows test and some actual bugs for unclosed file readers.
release 0.3.1 (#477) Signed-off-by: Krasi Georgiev <kgeorgie@redhat.com>
2018-12-13 14:02:32 +00:00
Release v0.3.0 (#464)
2018-12-04 13:50:11 +00:00
## 0.3.0
- [CHANGE] `LastCheckpoint()` used to return just the segment name and now it returns the full relative path.
- [CHANGE] `NewSegmentsRangeReader()` can now read over miltiple wal ranges by using the new `SegmentRange{}` struct.
- [CHANGE] `CorruptionErr{}` now also exposes the Segment `Dir` which is added when displaying any errors.
- [CHANGE] `Head.Init()` is changed to `Head.Init(minValidTime int64)`
- [CHANGE] `SymbolTable()` renamed to `SymbolTableSize()` to make the name consistent with the `Block{ symbolTableSize uint64 }` field.
- [CHANGE] `wal.Reader{}` now exposes `Segment()` for the current segment being read and `Offset()` for the current offset.
Add a tsdbutil command to analyse churn etc. (#478) This reports the cardinality of each label, the total number of label pairs, and how much series worth of time is "uncovered" by series data. Which is basically how much churn there is. Signed-off-by: Brian Brazil <brian.brazil@robustperception.io>
2018-12-28 17:06:12 +00:00
-[FEATURE] tsdbutil analyze subcomand to find churn, high cardinality, etc.