Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upScrape fails with connection reset by peer #2495
Comments
This comment has been minimized.
This comment has been minimized.
|
Do you have reason to believe that Prometheus is acting incorrectly here? |
This comment has been minimized.
This comment has been minimized.
|
Problem solved on server side. Go HTTP client handle connection closing correctly. |
iobestar
closed this
Mar 14, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
iobestar commentedMar 13, 2017
I have targets migrated from Jetty 9.2 to 9.3 and scraping start failing with exception: connection reset by peer.
If Jetty 9.2 is used on target then scraping doesn't fail.
It seems that Go http client in Prometheus Server doesn't work well with Jetty 9.3 "half-closed" connections.
This is probably related to eclipse/jetty.project#359
Can anyone else confirm this issue?