Why Timeseries Bucket count is different on 2 independent environment with same data

Working with Data
, , , ,
4

Hello @Kushagra_Kesav
I have digged up further address the issue and found out that iterating Daily Collections causing this issue as I decide on our architectural decision. My issue is very similar to this topic.

I was trying to understand the issue and shared it via StackExchange Community,

wiredtiger - MongoDb Timeseries Data at high Load Causes Cache Pressure in Time - Database Administrators Stack Exchange.

I guess I address this issue so far, my proposal to fix it on the Mongo feedback,

I do really like this Timeseries Feature with Mongo and Would be great to enhance it and support any architectural design.

So we basically no need to restart or trying to force wiredtiger to put the datas into Disk for buckets which we left behind If we decide iterating daily.
Thank you.