Current archiving flow can bring certaing ammount of problems when archiving segments on instances which are 2-3-4 years old. During normal flow of cron archiving, there will always be only last 2 years processed. Adding new segment(s) can bring up two following problems for archive process:
The goal of this ticket is to decide best approarch to this issue and hopefully plan implementation for improvement
One idea to handle thosse issues is:
Thanks for the suggestion! we'll investigate this in 2.11.0 sprint, once we have #5363
Segment does not necessarily need to be archived since the beginning of time. I would suggest adding an extra set of properties: start-date and end-date of the segment. This way the archiving would not need to calculate all historic data.
First step to solve this issue will be #7223
If that issue does not solve the problem all together, let's discuss again what solution we could put in place :+1: