dockerstats | Simple Docker info and stats library for node | Continuous Deployment library

Meteor publications work in a way that is causing you this problem...

Data is published selectively from the server. But once published, it is not removed from the client side collection. So your client side data is growing over time as more and more data is published.

So you will need to do a filter in your client code (ie your subscription) as well. That will fix the problem. It will, however, rely on exact time synchronisation between client and server.

Over time your client side collection will also grow, and eventually cause you some memory/performance problems. So you might want to consider a different approach. You could create a separate collection which is managed by the server, to just contain the last 10s of data. Older data is deleted, and the client subscription is simple, with no need for precise clock sync between client and server.

According to the docs, you need to pass in an empty object to delete the whole collection. So, the below would remove all students from the Students collection:

Mongodb stores all time data in utc. So if you use local time, you should convert it back on reading. Or let your mongodb driver to do it. Read more about it (with suggested workaround) here:

https://docs.mongodb.com/v3.4/tutorial/model-time-data/