[SERVER-22639] RocksDB storage engine needs to support JournalListener Created: 16/Feb/16 Updated: 06/Dec/22 Resolved: 24/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
In 3.2 replication introduced the journal listener, which is used to tell the replication subsystem when a particular log op has been persisted locally. Without it, read concern majority is calculating the journalled committed optime without taking into account primary's contribution. Because of this, the RocksDB storage engine needs to support the journal writer. Note that this task might become unnecessary due to |
| Comments |
| Comment by Igor Canadi [ 24/Feb/16 ] |
|
Looks fixed, all RocksDB tests are green. |
| Comment by Igor Canadi [ 18/Feb/16 ] |
| Comment by Igor Canadi [ 17/Feb/16 ] |
|
I'm on it! |