Last modified: 2014-02-21 22:50:28 UTC
CirrusSearch's in place reindex is designed around in process updates, not job updates. This means some updates will be missed. Instead of trying to catch up on updates like we do now, it might be better to have the reindex process pause the updates somehow.