[SERVER-39651] drop pending collection dose not clear collections since server upgraded to version 3.6.6 Created: 18/Feb/19 Updated: 17/Oct/19 Resolved: 19/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | aviv | Assignee: | Bruce Lucas (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
Hey, MongoDB upgraded to version 3.6.6 (was 3.4) mongodb client 3.4.2
Since the server has been upgraded. the storage keep growing on secondaries and keep the drop collections on "pending" state. only If I take the secondary down its starting to drop the collections: I STORAGE [initandlisten] Found drop-pending namespace .system.drop
Can you please lead to any direction ?
thanks! |
| Comments |
| Comment by Kelsey Schubert [ 19/Feb/19 ] |
|
Thanks for the update, aviv10. I'm resolving this ticket as a duplicate of |
| Comment by aviv [ 19/Feb/19 ] |
|
worked like magic. thanks a lot! |
| Comment by Bruce Lucas (Inactive) [ 18/Feb/19 ] |
|
aviv10, can you check whether your replica set is still using protocol version 0? This was deprecated in v3.6 and support has been removed in v4.0. If so you are probably encountering Bruce |