Bug#943884: prometheus: Loosing all the historical data on upgrade to version 2+
On 31/10/2019 12:54, Martina Ferrari wrote: > Unless there is something broken, you should have gotten a notice while > upgrading that informs you of the breaking changes. Also, did it remove > you data or just ignored it? Plus, you should have gotten a debconf dialog explaining this and offering whether to delete the old data or not. -- Martina Ferrari (Tina, the artist formerly known as Tincho)
Bug#943884: prometheus: Loosing all the historical data on upgrade to version 2+
Hi, On 31/10/2019 11:11, root wrote: > I've blindly upgraded prometheus 1.5.2+ds-2+b3 to 2.7.1+ds-3+b11 and > this automatically removed all my historical data from > /var/lib/prometheus/metrics/. I had to rollback because new version > requires new configuration and finding solution on keeping historical > data. As developers provided no way to convert to new format most > probable solution will be to stuck on pre 2.0 version. Dramatic > changes like that are dangerous and should not happen so easy. Unless there is something broken, you should have gotten a notice while upgrading that informs you of the breaking changes. Also, did it remove you data or just ignored it? This is the text you should have gotten from APT: prometheus (2.0.0+ds3-1) unstable; urgency=medium BREAKING CHANGES The data format in Prometheus 2.0 has completely changed and is not backwards compatible with 1.x. Prometheus 2 will create a new data directory in /var/lib/prometheus/metrics2. The old data in /var/lib/prometheus/metrics can not be read by the new version. There is no conversion tool; if you want to retain access to the old data, it is necessary to run a separate Prometheus 1.x instance on that data directory. (This package makes no provision to allow this.) -- Martina Ferrari (Tina, the artist formerly known as Tincho)
Bug#943884: prometheus: Loosing all the historical data on upgrade to version 2+
Package: prometheus Version: 1.5.2+ds-2+b3 Severity: important Dear Maintainer, I've blindly upgraded prometheus 1.5.2+ds-2+b3 to 2.7.1+ds-3+b11 and this automatically removed all my historical data from /var/lib/prometheus/metrics/. I had to rollback because new version requires new configuration and finding solution on keeping historical data. As developers provided no way to convert to new format most probable solution will be to stuck on pre 2.0 version. Dramatic changes like that are dangerous and should not happen so easy. -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable'), (81, 'testing'), (80, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages prometheus depends on: ii daemon 0.6.4-1+b2 ii libc62.28-10 ii libjs-bootstrap 3.4.1+dfsg-1 ii libjs-eonasdan-bootstrap-datetimepicker 4.17.47-3 ii libjs-jquery 3.3.1~dfsg-3 ii libjs-jquery-hotkeys 0~20130707+git2d51e3a9+dfsg-2 ii libjs-moment 2.24.0+ds-1 ii libjs-mustache 2.3.2-1 ii libjs-rickshaw 1.5.1.dfsg-2 Versions of packages prometheus recommends: ii prometheus-node-exporter 0.17.0+ds-3+b11 prometheus suggests no packages. -- Configuration Files: /etc/default/prometheus changed [not included] /etc/prometheus/prometheus.yml changed [not included] -- debconf information: prometheus/remove-version1-database: true
