Info

checkForInterruptNoAssert calls during handleRequest for getMores that result in ClientDisconnect (being thrown and markKilled) cause an issue where a new killCursor opCtx is created and the old opCtx is not delisted. Find a way to change this if condition for this exact condition, possibly making a more clear distinction between thrown statuses and opCtx killStatus. ServiceEntryPointImpl delist logic

Top User Comments

xgen-internal-githook commented on Thu, 12 Oct 2023 17:57:53 +0000: Author: {'name': 'Alex Li', 'email': 'alex.li@mongodb.com', 'username': 'lia394126'} Message: SERVER-80001 Delist opCtx during ClientDisconnect during getMores (cherry picked from commit a538c12b922ef26e721135be51badcff68dfc336) Branch: v7.0 https://github.com/mongodb/mongo/commit/ac01949d1043efecb1fbd3d2e7d6169e33969d96 xgen-internal-githook commented on Thu, 24 Aug 2023 20:41:28 +0000: Author: {'name': 'Alex Li', 'email': 'alex.li@mongodb.com', 'username': 'lia394126'} Message: SERVER-80001 Delist opCtx during ClientDisconnect during getMores Branch: master https://github.com/mongodb/mongo/commit/a538c12b922ef26e721135be51badcff68dfc336

Steps to Reproduce