[SERVER-56556] create collection coordinator waits on wrong opTime to be mojority committed Created: 01/May/21 Updated: 29/Oct/23 Resolved: 01/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | Backlog |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Create collection coordinator explicitly wait for majority write concern after creating the shard key index. The problem is that if the index was already created no write will be performed , in this case the last op time on the current client could be a very old op time, associated with the last write performed by a previous task scheduled on that thead. So the solution would be to properly set the last op time before to wait it to be majority written. |
| Comments |
| Comment by Githook User [ 01/May/21 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |