When cos, roles, and views are betxn enabled, they can cause deadlocks - the thread that updates the cache can deadlock trying to search while there is another thread with an update txn in progress. In addition, cos, roles, and views suffer from the problem that if you do a search immediately after an update operation, you may not get back the results you expect if the cache has not yet been updated. To solve both of these problems, cos, roles, and views should be made betxn aware by doing the cache update inside the transaction, so that the search can use the update txn. There may be other optimizations too, such as not searching for everything in the entire tree every time an update happens. See the comments from rbyrne in cos_cache.c
set default ticket origin to Community
Added initial screened field value.
Mark as duplicate of #351.
Metadata Update from @nhosoi:
- Issue assigned to rmeggins
- Issue set to the milestone: 1.3.0.a1
to comment on this ticket.