We're updating the issue view to help you get more done. 

Cluster - handlers can be skipped if value changes during retries

Description

When we retry the consul handlers, we refetch the value - if it just so happens, that the value changes after one of the handlers has finished successfully, but another is still retrying, the successful one might not be called at all with the most recent value.

Example:

  • a watched value changes, handlers A and B are set to run

  • A passes on the first try, but B throws an error so it's retried

  • after 5 retries, the value changes again, so the next call of B will be with the new value

  • ...but A isn't called again at all, ever

Currently, this breaks the set-active system tests

Status

Assignee

Łukasz Maksymczuk

Reporter

Łukasz Maksymczuk

Labels

Severity

None

Bug Type

None

Target Version

None

Severity

None

Sprint

None

Fix versions

Affects versions

4.2