mirror of https://github.com/prometheus/prometheus
Browse Source
We were still fsyncing while holding the write lock when we cut a new segment. Given we cannot do anything but logging errors, we might just as well complete segments asynchronously. There's not realistic use case where one would fsync after every WAL entry, thus make the default of a flush interval of 0 to never fsync which is a much more likely use case.pull/5805/head
Fabian Reinartz
7 years ago
4 changed files with 30 additions and 32 deletions
Loading…
Reference in new issue