Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.0, 4.0.0, 4.5.0
-
Untriaged
-
Unknown
Description
PendingOpsNotification Task is using the priority of VBMemoryDeletionPriority (set to 6) as opposed to PendingOpsNotification (set to 0).
This means that it has a lower priority than it is supposed to have. (a lower number means higher priority).
The PendingOpsNotifcation task is a NONIO_TASK and is responsible for performing notifyIOComplete. Therefore If the NONIO thread is busy we could be delayed sending the notification.
Attachments
Issue Links
- blocks
-
MB-19612 4.5.1 Minor Release
-
- Closed
-
| For Gerrit Dashboard: MB-19836 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 64711,1 | MB-19836: Correctly set PendingOpsNotifcation task priority | master | ep-engine | Status: ABANDONED | 0 | 0 |
| 64712,1 | MB-19836: Correctly set PendingOpsNotifcation task priority | watson | ep-engine | Status: ABANDONED | 0 | 0 |
| 64714,2 | MB-19836: Correctly set PendingOpsNotifcation task priority | watson | ep-engine | Status: MERGED | +2 | +1 |
| 64767,1 | Merge remote-tracking branch 'couchbase/watson' | master | ep-engine | Status: MERGED | +2 | +1 |