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

An archive invalidation is never removed even though the data is being archived for the period regularly #19338

Open
tsteur opened this issue Jun 10, 2022 · 0 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc.

Comments

@tsteur
Copy link
Member

tsteur commented Jun 10, 2022

On the cloud we have a monitoring active that we're emailed should archive invalidations for some reason not be processed within a given amount of days to make sure data is always available etc.

We're receiving emails regularly especially from one account where we have for example this invalidation:

image

However, we can see that there is indeed an archive for this period, and the data is available in the UI.

image

We would have therefore expected this invalidation to be removed by the system at some point. Or we would have expected it wouldn't schedule a new archive invalidation because one already exists and then next time it would process and remove this old archive invalidation.

The referenced segment exists and is not deleted. The referenced site also still exists. And the archive has data.

Segment info:
image

I ran core:archive with -vvv to get debug log output and this is what's happening:

DEBUG [2022-06-10 08:45:25] 8255 cloud Found invalidation with usable archive (not yet outdated, ts_archived of existing = 2022-06-10 08:45:19, now = 2022-06-10 08:45:25) skipping until archive is out of date: [idinvalidation = 727693, idsite = 1, period = year(2022-01-01 - 2022-12-31), name = donec80ad4816bb0402b54d7c77c5f90b151, segment = ...]

Meaning Matomo might only remove this entry after this year is completed maybe meaning it might only delete it in 2023-01-01? This would mean though that this invalidation will never be removed. The same seems to be happening for the monthly archive:

image

And it would only be removed by the beginning of the next month. It kind of defeats the purpose a bit and it's this way not clear if the system has a problem or not.

Interestingly, this same behaviour is not happening in other accounts and couldn't find any such similarly old entries. There they were deleted somehow correctly.

As a result, we're receiving emails daily about this error. We could now just remove this invalidation manually. However, next time this happens again the devops team will spend hours again troubleshooting what's happening together with core and plugin team members.

This is happening with latest Matomo (4.10) and PHP 8.

cc @JasonMortonNZ

@tsteur tsteur added the Bug For errors / faults / flaws / inconsistencies etc. label Jun 10, 2022
@bx80 bx80 added this to the For Prioritization milestone Jun 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

2 participants