[SERVER-19821] Targeter fails after drop Created: 07/Aug/15 Updated: 06/Dec/22 Resolved: 09/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.1.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | pm-1051-legacy-tickets | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Assigned Teams: |
Sharding
|
| Operating System: | ALL |
| Steps To Reproduce: | remove this line and run concurrency suite: |
| Participants: |
| Description |
|
Write commands results with errors "could not target insert in collection map_reduce_drop.coll80; no metadata found" after the database was dropped in the fsm test specified in the steps above. |
| Comments |
| Comment by Andy Schwerin [ 07/Aug/15 ] |
|
renctan, can you please add some relevant details to the description? |