1) Currently reindexing logic is done within the index while holding it's lock
2) This should be possible to do outside of the write lock.
ideally we would want a per consensus notification reindexer to perform the reindex inside the index processor and then simply supply the result to the index for committance to its Db.
A per consensus notification approach should be preferred, as
1) the index processor processes on a per notification basis,
2) reindexer looping and logic can supply reindexed notification conversion results separately for each index wanting information from a certain notification, without potentially re-preforming looping and certain logic from scratch.
1) Currently reindexing logic is done within the index while holding it's lock 2) This should be possible to do outside of the write lock.
ideally we would want a per consensus notification reindexer to perform the reindex inside the index processor and then simply supply the result to the index for committance to its Db.
A per consensus notification approach should be preferred, as