[SERVER-23581] Temporarily change instances of count() on a config database collection in JS tests to itcount(), and later revert Created: 06/Apr/16  Updated: 06/Dec/22  Resolved: 07/Jul/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-22131 Count, write, aggregate and group com... Closed
Assigned Teams:
Sharding
Sprint: Sharding 13 (04/22/16), Sharding 14 (05/13/16), Sharding 15 (06/03/16)
Participants:
Linked BF Score: 0

 Description   

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()..


Generated at Thu Feb 08 04:03:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.