[SERVER-74720] The default 'shardingStatistics' serverStatus section takes locks Created: 09/Mar/23  Updated: 29/Oct/23  Resolved: 13/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, 6.0.6, 5.0.17, 6.3.1

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Pol Pinol
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
is caused by SERVER-68576 We need to know how many sharded coll... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.3, v6.0, v5.0
Sprint: Sharding EMEA 2023-03-20
Participants:
Linked BF Score: 161

 Description   

Default serverStatus sections are used by FTDC and also for emergency debugging. Because of this, we should try to ensure that they can always make forward progress. Taking locks or performing I/O runs the risk that a server in some degraded state will not be able to collect FTDC metrics and thus will impede diagnostics.

The shardingStatistics serverStatus section is included by default if the node is a cluster node, but it also takes locks. We should be able to read the estimated number of documents using the lock-free variant of the function.



 Comments   
Comment by Githook User [ 12/Apr/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-74720 The default 'shardingStatistics' serverStatus section takes locks

(cherry picked from commit f18e1f8b2d5f5988fa7c6e18e343c9c85589bae9)
Branch: v6.3
https://github.com/mongodb/mongo/commit/46832492a977b636552649f00cfdb9e2c242cebf

Comment by Githook User [ 12/Apr/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-74720 The default 'shardingStatistics' serverStatus section takes locks

(partially cherry picked from commit f18e1f8b2d5f5988fa7c6e18e343c9c85589bae9)
Branch: v5.0
https://github.com/mongodb/mongo/commit/4936d07dc233aff1529456527a1efc950cd85d61

Comment by Githook User [ 28/Mar/23 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: Revert "SERVER-74720 The default 'shardingStatistics' serverStatus section takes locks"

This reverts commit 008395b28d83011a03033cd57848d862263bfb60.
Branch: v5.0
https://github.com/mongodb/mongo/commit/4b24b3e39f6b586d97bc9ff953c00607e6a4c6c9

Comment by Githook User [ 21/Mar/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-74720 The default 'shardingStatistics' serverStatus section takes locks

(cherry picked from commit f18e1f8b2d5f5988fa7c6e18e343c9c85589bae9)
Branch: v6.0
https://github.com/mongodb/mongo/commit/45b8db3ad4dca2fb85e9d6671e9bb171b435cb26

Comment by Githook User [ 21/Mar/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-74720 The default 'shardingStatistics' serverStatus section takes locks

(cherry picked from commit f18e1f8b2d5f5988fa7c6e18e343c9c85589bae9)
Branch: v5.0
https://github.com/mongodb/mongo/commit/008395b28d83011a03033cd57848d862263bfb60

Comment by Githook User [ 20/Mar/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-74720 The default 'shardingStatistics' serverStatus section takes locks
Branch: master
https://github.com/mongodb/mongo/commit/f18e1f8b2d5f5988fa7c6e18e343c9c85589bae9

Generated at Thu Feb 08 06:28:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.