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

On Thu, 10 Sep, 2020, 6:31 pm Ben Kochie, <[email protected]> wrote:

> "HTTP Superflous exception"
>
> What is this? Do you have a link to a github issue?
>
> On Thu, Sep 10, 2020 at 2:47 PM [email protected] <
> [email protected]> wrote:
>
>> *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
>>
>>
>> --
>> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/prometheus-users/7e859d19-0e7d-4f66-837b-2ca33d747adcn%40googlegroups.com
>> <https://groups.google.com/d/msgid/prometheus-users/7e859d19-0e7d-4f66-837b-2ca33d747adcn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/CAA6KEsmotM_q_3iwdWjOQ601bhvHrVBZqH1zB_nJfW%2BFGfGqnA%40mail.gmail.com.

Reply via email to