[SERVER-7536] fsyncUnlock should indicate how many unlock calls are left/required. Created: 01/Nov/12 Updated: 06/Dec/22 Resolved: 08/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.2.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ben McCann | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Orig description remove; see comment below from Ben. |
| Comments |
| Comment by James Wahlin [ 08/Mar/17 ] |
|
This was implemented under |
| Comment by Kevin Pulo [ 03/Mar/17 ] |
|
I think this is fixed now via the fix that went in on |
| Comment by Scott Hernandez (Inactive) [ 01/Nov/12 ] |
|
Re-opening with new description |
| Comment by Scott Hernandez (Inactive) [ 01/Nov/12 ] |
|
For every corresponding lock, you must unlock. Think of it more like a counter where a locks is +1, and an unlock is -1 and you must be at 0 to be unlocked. |
| Comment by Ben McCann [ 01/Nov/12 ] |
|
I suppose the current behavior could make sense, but the messaging isn't very good. E.g. if two processes each lock the db, do some operation, and then unlock it would make sense that you wouldn't want one process unlocking in the middle of the other process operating. However the fact that fsyncUnlock says "unlock completed" is very unintuitive in that case. It would be better if it said something like "locks remaining: 1" |