Closed Bug 1091730 Opened 11 years ago Closed 11 years ago

Disable zlb timeouts

Categories

(Webtools :: Pulse, defect)

Product:
Webtools
Component:
Pulse
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: mcote, Assigned: cliang)

Details

(Whiteboard: [kanban:webops:https://kanbanize.com/ctrl_board/4/1810] [qa-automation-blocked])

Zeus is currently set to terminate connects after 5 minutes of inactivity. However, it's entirely reasonable for no messages to be consumed for long periods of time on low-activity exchanges (or with restrictive filters), so we should just turn the timeouts off altogether.
Whiteboard: [qa-automation-blocked]
Mark, can we please get this done sooner than later? Thanks.
Flags: needinfo?(mcote)
I have no direct control over zlb; pinging cyliang.
Assignee: nobody → cliang
Flags: needinfo?(mcote)
Whiteboard: [qa-automation-blocked] → [kanban:webops:https://kanbanize.com/ctrl_board/4/1810] [qa-automation-blocked]
On the production pulse load balancer configuration, I changed the timeout value (i.e how long a connection should wait before closing itself if it has received no data) from 300 seconds to 0 (no time out). The total amount of time a transaction can take (from open to close) is already set to 0 (no time out).
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Thank you for this quick change! I checked our pulse listener on Mozmill-CI staging and the timeouts each 5 minutes have stopped.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.