Hey there,
After updating synced-cron, we were getting 100% cpu usage due to this query made by synced-cron, which was not an issue before. I don't think the query is well-formed, $exists: false is not indexable. Maybe having a default false value would help, as well as a specific index on this.
Hey there, After updating synced-cron, we were getting 100% cpu usage due to this query made by synced-cron, which was not an issue before. I don't think the query is well-formed,
$exists: false
is not indexable. Maybe having a default false value would help, as well as a specific index on this.