Jira (PUP-7022) The HTTP report processor should timeout requests that take too long

[Erik Hansen (JIRA)]

Erik Hansen created an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long Issue Type: Bug Assignee: Unassigned Created: 2016/12/16 9:21 AM Priority: Normal Reporter: Erik Hansen The HTTP report processor currently does not timeout if the endpoint does not reply. This has the effect that a JRuby is tied up indefinitely, and not returned to the pool. This can quickly tie up all available JRubies and prevent further work being done by the puppetserver process. Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Eric Sorenson (JIRA)]

Eric Sorenson updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Eric Sorenson Team: Agent & Platform

Add Comment

[Eric Sorenson (JIRA)]

Eric Sorenson updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Eric Sorenson Sprint: AP Grooming 2017-02-01

Add Comment

[Eric Sorenson (JIRA)]

Eric Sorenson updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Eric Sorenson Component/s: Networking Services

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Geoff Nichols Sprint: AP Grooming  On-Deck

Add Comment

[Geoff Nichols (JIRA)]

[Geoff Nichols (JIRA)]

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Geoff Nichols Sprint: Agent Grooming On-Deck

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Branan Riley Labels: triaged

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Branan Riley Team: Agent Systems Engineering

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Branan Riley Component/s: Puppet Server

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Maggie Dreyer Labels: http

Add Comment

This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Josh Cooper Component/s: Puppet Server

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Josh Cooper Team: Coremunity Froyo

Add Comment

This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)

[David McTavish (Jira)]

David McTavish updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: David McTavish Labels: http nice-to-have reliability

Add Comment

[David McTavish (Jira)]

David McTavish commented on PUP-7022

Re: The HTTP report processor should timeout requests that take too long if we do this, we should preserve the default behavior of having no timeout, but allow users to over-ride this

Add Comment

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-7022

Re: The HTTP report processor should timeout requests that take too long

If the report processor hangs, takes too long, agent runs (every 30 minutes) will start to run over each other. My preference would be to implement whatever timeout Charlie Sharpsteen recommends. If the report processor actually takes more than 30 minutes to process the report, then something is very wrong with the puppet infrastructure.

Add Comment

[David McTavish (Jira)]

David McTavish commented on PUP-7022

Re: The HTTP report processor should timeout requests that take too long

thats fair Josh Cooper my worry was if users were doing something strange like streaming data over HTTP2 but now my understanding is this is communication between our systems, it should have a deterministic duration

Add Comment

[David McTavish (Jira)]

David McTavish updated an issue

Puppet / PUP-7022

The HTTP report processor should timeout requests that take too long

Change By: David McTavish Priority: Normal Low

Add Comment

This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)

[David McTavish (Jira)]

David McTavish updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: David McTavish Epic Link: SERVER- 2122 3178

Add Comment

[David McTavish (Jira)]

David McTavish updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: David McTavish Sprint: Froyo - On Deck

Add Comment

[David Piekny (Jira)]

David Piekny updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: David Piekny

Sprint: Froyo - On Deck

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long

Change By: Josh Cooper Team: Froyo Phoenix

Add Comment

This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)