Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v2 "blast from the past" on sr_poll failover. #1184

Open
petersilva opened this issue Aug 23, 2024 · 2 comments
Open

v2 "blast from the past" on sr_poll failover. #1184

petersilva opened this issue Aug 23, 2024 · 2 comments
Labels
bug Something isn't working v2only only affects v2 branches. wontfix This will not be worked on (outside development scope) work-around a work-around is provided, mitigating the issue.

Comments

@petersilva
Copy link
Contributor

when upgrading from v2.21 -> v2.24.08 ... we thought we had allowed all the sr_poll file listings to update properly before switching the vip, but we got a blast from the past anyways.

We do not understand why this happenned.

@petersilva petersilva added bug Something isn't working wontfix This will not be worked on (outside development scope) v2only only affects v2 branches. labels Aug 23, 2024
@andreleblanc11
Copy link
Member

andreleblanc11 commented Aug 23, 2024

Another weird behaviour noticed (not sure if it's the same issue or not)

Observed behaviour

  • We will be updating a server that has v2.21.04 of sarracenia v2 to a v2.23.07 and up.
  • For some polls, once we start them back up, they will re-post all the files it founds on the remote server.
  • Normally the ls file is supposed to catch duplicated files and avoid such behaviour.
  • For whatever reason, the poll looks to be ignoring the ls file entries and keep posting all of the files found.
  • This is slightly different than what is described in the issue description. It will keep having "blasts from the past" until the configuration is restarted and has its cache cleared.
  • This doesn't impact all polls, only some specific ones. We're not sure why this is happening.

How to fix

  • Stop the poll
  • Delete all the files under the cache directory ~sarra/.cache/sarra/poll/my-config/*
  • Start the poll
  • UPDATE : This fix DOESN'T ALWAYS WORK

Impact

  • Luckily the impact isn't that big for the moment. It looks like after restarting the config and deleting the cache that the poll correctly constructs the ls file.

@petersilva
Copy link
Contributor Author

this might be just a plain problem with v2 polls in the latest release, but only affecting some configurations.
It is not just when starting up after an upgrade. It seems to recur once in a while if the poll runs for a long time.
still clarifying.

work-around: upgrade flow to sr3.

@petersilva petersilva added the work-around a work-around is provided, mitigating the issue. label Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v2only only affects v2 branches. wontfix This will not be worked on (outside development scope) work-around a work-around is provided, mitigating the issue.
Projects
None yet
Development

No branches or pull requests

2 participants