[SERVER-72879] Recreation of same database with different cases could lead to database unavailability Created: 16/Jan/23 Updated: 27/Oct/23 Resolved: 25/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Steps To Reproduce: |
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
If two databases with same name but different cases (e.g.: DB1, db1) are dropped and created concurrently some shards could end up with inconsistent in-memory metadata causing database unavailability until the affected node is restarted. |
| Comments |
| Comment by Tommaso Tocci [ 25/Jan/23 ] |
|
Fixed by |