unshardCollection fails with NamespaceNotFound if the collection is already unsharded

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • Fully Compatible
    • ClusterScalability 2Mar-16Mar
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, running unshardCollection against an unsharded collection fails with NamespaceNotFound. This can be quite confusing given that the collection does exist. It should instead fail with NamespaceNotSharded. 

            Assignee:
            Jordan Glassley
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: