Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Pipeline start returns 502

Description

Currently, flow control causes appfabric to return 429 if number of concurrently launching/running is abve certain threshold.

However, if pipeline start is retried long enough upon getting 429, caller may receive 502 instead of 429.

Release Notes

Fixed an issue in flow control that caused Appfabric to return 5xx error code in rare scenarios instead of 429 (Too Many Requests Error) if the number of concurrently launching or running pipelines were above certain thresholds.

Activity

Show:

Masoud Saeida ArdekaniJuly 22, 2022 at 4:10 PM

Yes, would be good to have a release node for this.

Robin RielleyJuly 22, 2022 at 3:51 PM

Do we need a release note?

Vinisha ShahJune 24, 2022 at 7:31 PM

Masoud Saeida ArdekaniJune 22, 2022 at 5:09 PM

The issue is caused since flow control wants to count all program controllers with RUNNING state. However, DelayedProgramController.getState() call is blocked until ProgramController is set through setProgramController which happens once launch is finished.

Therefore, when a new launch request comes in, it waits until all inflight requests are launched. This delays the response, and results in different 5xx errors.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Affects versions

Triaged

No

Components

Fix versions

Due date

Priority

Created June 10, 2022 at 7:35 PM
Updated November 29, 2022 at 7:19 PM
Resolved June 30, 2022 at 9:14 PM

Flag notifications