Skip to:

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

enable async polling by default

Description

Asynchronous polling, which was added as an experimental feature in Horizon 32, should be the default in Horizon 33

Acceptance / Success Criteria

None

Attachments

4

Activity

Show:

Ronny Trommer February 15, 2024 at 10:10 AM
Edited

Here is an example of a symptom I’ve seen in H33.0.0 deployment with async polling enabled, when the poller had to deal with some stress due to latency.

The correct situation would be just the nodeDown event and not the nodeLostService events. I think we can reproduce this problem in a smaller environment using small “polls in flight” and thread numbers.

I tried the same with the “asynPolling” disabled and I wasn’t able to reproduce this behavior.

I think it would be helpful to figure out if we can reproduce this in a test case.

Ronny Trommer February 14, 2024 at 3:50 PM

I can spend some time to figure out if I can reproduce what I’ve experienced during a support session, not having reliable nodeDown / interfaceDown events and we where forced to disable the node outage processing feature in the poller-configuration.xml

Benjamin Reed February 14, 2024 at 3:45 PM
Edited

this has been reverted, we need to revisit it after looking into the node outage issue reported

Details

Assignee

Reporter

Sprint

Fix versions

Priority

Parent

PagerDuty

Created June 7, 2023 at 4:10 PM
Updated April 9, 2024 at 4:28 PM