Prometheus Latest Version Upgrade - Help/Guidance Needed

dineshnithy...@gmail.com

unread,

Sep 10, 2020, 8:47:09 AM9/10/20

to Prometheus Users

Problem context:

we are currently running with year old version of prometheus version-2.13 which was less error prone with HTTP Superflous exception compare to the near latest version till 2.17 and due to the same reason we are still persisting with 2.13 version

Options:

Perhaps, we wanted to move ahead with latest version of prometheus and get it benchmarked and potentially considering 2.20.1 which would possess rich scalable features like less memory consumption (3kb for each time series) and faster restarts due to Mmap feature

Just wanted to get some guidance on which version was apparently was very stable accommodating latest features

Ben Kochie

unread,

Sep 10, 2020, 9:01:15 AM9/10/20

to dineshnithy...@gmail.com, Prometheus Users

"HTTP Superflous exception"

What is this? Do you have a link to a github issue?

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/7e859d19-0e7d-4f66-837b-2ca33d747adcn%40googlegroups.com.

Dinesh N

unread,

Sep 10, 2020, 10:56:06 AM9/10/20

to Ben Kochie, Prometheus Users

Ben - This issue happens under heavy load - there is a ticket already in GitHub and acknowledged by some of them having similar issue - https://github.com/prometheus/prometheus/issues/6139

Dinesh N

unread,

Sep 12, 2020, 3:48:39 AM9/12/20

to Ben Kochie, Brian Candler, Brian Brazil, Prometheus Users

Can someone please guide me through on this hassle

Bjoern Rabenstein

unread,

Sep 23, 2020, 1:43:41 PM9/23/20

to Dinesh N, Ben Kochie, Prometheus Users

On 10.09.20 20:25, Dinesh N wrote:
> Ben - This issue happens under heavy load - there is a ticket already in GitHub
> and acknowledged by some of them having similar issue - https://github.com/
> prometheus/prometheus/issues/6139

Is this issue causing any actual trouble to you except that this line
is logged? My understanding is, this is more a warning that some
codepath is acting on wrong expectations, but it's not actually
causing any harm here. I would be very interested if any other issues
arise from that (in which case, please follow up to the issue).

--
Björn Rabenstein
[PGP-ID] 0x851C3DA17D748D03
[email] bjo...@rabenste.in

Reply all

Reply to author

Forward