[SERVER-9297] Btree index counters are not thread-safe Created: 09/Apr/13  Updated: 04/Jun/13  Resolved: 04/Jun/13

Status: Closed
Project: Core Server
Component/s: Diagnostics, Index Maintenance
Affects Version/s: 2.2.4, 2.4.1
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Tad Marshall Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-9393 Very, very fast counters Backlog
Operating System: ALL
Participants:

 Description   

Accounting errors for btree index counters are likely in a multi-client situation because the counters are not atomic and are not locked while being updated.

These are not critical counters and they were only sampled in versions before version 2.2, but it would be nice for them to be more reliable.



 Comments   
Comment by Scott Hernandez (Inactive) [ 04/Jun/13 ]

Seems like we can use the existing ServerStatusMetricField for these without anything new.

Comment by Ian Whalen (Inactive) [ 04/Jun/13 ]

we should roll this fix into the work Paul is doing for fast counters - linking these tickets as such.

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