ISSUE SUMMARY
On a sharded cluster, a shard may crash when a splitChunkCommand operation is issued on a non-existing namespace. One way to reproduce this is to connect to a shard, drop a sharded collection and then issue the split command through mongos on that collection.
Non-sharded systems are not affected by this issue.
USER IMPACT
The shard where the namespace doesn't exist logs a stack trace in the log and crashes.
WORKAROUNDS
N/A
AFFECTED VERSIONS
MongoDB 2.4 production releases up to 2.4.10 are affected by this issue.
FIX VERSION
The fix is included in the 2.4.11 production release.
RESOLUTION DETAILS
Do not perform any split operations if the namespace doesn't exist on a given shard.