Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.1.2
Affects Version/s: None
Component/s: Sharding
Labels:
None

Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

When dropping sharded collections on mongod, we need to invalidate all connection state for that namespace. If the collection gets recreated, this information will be stale.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

multi_coll_drop.js
Nov 13 2011 07:22:35 PM UTC
1 kB
Greg Studer

depends on

SERVER-5918 invalid memory writes in sharding test suite

Closed

is depended on by

SERVER-5150 drop collection : now errors with sharding

Closed

is duplicated by

SERVER-5753 Assertion failures when a sharded collection is dropped and sharded again and reused.

Closed

is related to

SERVER-4429 When moving primary need to inform all other mongoses

Closed

Assignee:: Greg Studer (Inactive)
Reporter:: Greg Studer (Inactive)
Participants:: auto, David Nesbitt, Eliot Horowitz, Greg Studer, Y. Wayne Huang
Votes:: 7 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Nov 11 2011 06:11:44 PM UTC
Updated:: Jul 11 2016 06:32:31 PM UTC
Resolved:: Jun 12 2012 08:39:26 PM UTC

Details

Description

Attachments

Attachments

Issue Links

Forms

Activity

People

Dates