|
After consulting with sulabh.mahajan@mongodb.com, who's looking into a broader class of WT cache pressure-related problems in the MongoDB server, I've decided to mark this ticket as dependent on WT-10958. That WT ticket would allow MongoDB to efficiently roll back the transactions that have been blocking eviction, covering the case of an offending transaction that's been sitting idle for most of its time.
Note that this ticket was initially marked as dependent on WT-8848; however, that WT ticket ended up implementing a different approach which doesn't meaningfully apply to SERVER-64982 any longer.
Based on the conversation in this server ticket, I've also filed DOCS-16283 to improve the documentation around multi-doc transactions during periods of untenable WT cache pressure.
|
|
connie.chen@mongodb.com, not really. SERVER-61909 changes the retry behaviour of a single large transaction after we get a WT_ROLLBACK error, the problem described here is more about the fact that a transaction may occupy a large portion of the cache, and not make any more calls into the WT api, and thus not get rolled back, blocking progress for other transactions.
|