Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-23581

Temporarily change instances of count() on a config database collection in JS tests to itcount(), and later revert

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • Sharding 13 (04/22/16), Sharding 14 (05/13/16), Sharding 15 (06/03/16)
    • 0

      Some JS tests are failing on the sharding_continuous_config_stepdown suite because count() on a config database collection is not retriable. This can be fixed by using itcount() instead, which does retry.

      Changes to any JS tests should be committed on this ticket, and then when SERVER-22131 (to make count() retriable) is completed these changes can be reverted.

      Differences between count() versus itcount():
      count() can count orphaned documents on sharded collections, whereas itcount() will filter out the orphans, which also takes longer. Config server is not sharded, so can use the cheaper count()..

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: