On 10.08.20 19:28, li yun wrote: > I check the historical data for a year, and occasionally some errors may cause > problems with Prometheus. The following is the error message > [...]
The log entries shown have nothing to do with querying. It looks more like your server crashed for some reason (perhaps OOMing, which might be triggered by your query) and therefore dumped stack traces of all the goroutines. The initial info-level log line is not a stack trace and looks more like something that shows up during startup. Perhaps an earlier crash left the TSDB files on disk in an unrecoverable state. First thing I would check is Prometheus's memory consumption while running the expensive query. You might need to give it more RAM. -- Björn Rabenstein [PGP-ID] 0x851C3DA17D748D03 [email] [email protected] -- 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/20200811122849.GW3395%40jahnn.
