Feb 4
2 / 2
Feb 25
Feb 24
Zaki_Syed
Feb 4

image
image967×227 9.47 KB

The Image clearly shows the archive criteria is for 200 days, but the Criteria that’s gets calculated is Wrong, which is shown as min and max date (MAX Date is calculated wrong).

19 days later
Shashank_LaudMongoDB Employee
Feb 24

I understand that you are observing the Max Date Field as 2023-12-07T05:54:17Z for the online archive on the namespace eco.Ecotron. You have an Age limit of 200, which means any data older than 200 days should be archived.

The Max Date Field represents the maximum date value among all documents in the archive.

I did checked your configuration and was could see you have a scheduled archival window configured,

In your case, the archiving schedule is set for 4 hours. As outlined in our documentation, if you specify a time window for the archival job, Atlas will continuously run the job during that window as long as there is at least 5 MiB of data to archive.

If you still see data in the Atlas cluster that is older than 200 days, it likely means that the online archive has not yet moved that data. To expedite the process, you may consider increasing the archival window to allow the jobs to run for a longer duration.


Want to read more? Browse other topics in MongoDB Atlas or view latest topics.