I just read in the old Kadira performance guide that $nearSphere operations are not supported by Meteor Oplog. This is a bummer to me, as our app is using geospatial queries heavily. And in fact, I can see in MontiAPM that my most important geospational pub is not using oplog at all.
So I am wondering if I can fix this by switching the app to Redis Oplog?
I haven’t tried this specific query for redis-oplog, but that might be difficult.
If docs B, C, and D are $nearsphere of A, and C changes, not sure how it can know to update redis-oplog to update A. Unless the $nearSphere queries are constant, then you can reverse $nearSphere on C and update redis-oplog with all the results.