[SERVER-39488] Test does not see the storage statistics in the profiled output . Created: 11/Feb/19  Updated: 29/Oct/23  Resolved: 13/Feb/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.0.9, 4.1.9

Type: Bug Priority: Major - P3
Reporter: Neha Khatri Assignee: Neha Khatri
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Storage Engines 2019-02-25
Participants:
Linked BF Score: 9
Story Points: 2

 Description   

The test wt_operation_stats.js looks for the storage statistics in the profiled output of the find operation. The find operation in the test is executed in two parts 1. find command itself and 2. getMore triggered by the find. The test always looks for the storage statistic in the last profiled command (getMore in this case). getMore does not always have the storage stats. It is the find command that always has the storage stats. Hence look for storage stats in the find command's profiled entry.



 Comments   
Comment by Githook User [ 03/Apr/19 ]

Author:

{'email': 'sulabh.mahajan@mongodb.com', 'name': 'Sulabh Mahajan', 'username': 'sulabhM'}

Message: SERVER-38239 Added getOperationStatistics() API to fetch storage stats from WiredTiger

(cherry picked from commit ba3894493a94ed3c18458f391ff181d57475f010)

SERVER-38240 Added storage statistics information into the slowop log messages.

(cherry picked from commit 86b6aca9fa1940e85bba87261d1494ef2c208a4a)

SERVER-38240 work around uint64_t conversion on s390x in WiredTigerOperationStats::fetchStats()

(cherry picked from commit 82161eec79fc74652dc07b1c83fe500dc4f95e79)

SERVER-38243 Test presence of the storage stats in slowop logs and system.profile.

(cherry picked from commit 3b4c6a689a3fdaa923d427ae112ea599513ef8ce)

SERVER-39026 Use correct type for retrieving WiredTiger stats

(cherry picked from commit 6a9a5855048df1f4796a4032276d01318c398691)

SERVER-39488 Look for storage stats in the find command's profiled entry.

The find command will always have the storage stats because the
test has created a collection with btree spanning multiple pages. Scanning
this collection after a server restart will trigger read from the disk
and have the disk read stats.

(cherry picked from commit 6125b5fb078a316854f0299b96b7d16eacb944de)

SERVER-39361 Synchronise collecting storage engine stats with shutdown

(cherry picked from commit bacb6b67706a2c057fcd0f76a38f416b225aa69a)

SERVER-39061 Fix the wt_operation_stats test to wait for the operation log to appear.

(cherry picked from commit 371197e4bab715a83272a4472e118ee5c5cbbf7c)

SERVER-39934 Fix locking for slow ops storage stats
SERVER-39654 Make slow ops storage stats work with transactions

(cherry picked from commit 23ca771f76f85638f23bca2a4a6ac196a81fdc21)
Branch: v4.0
https://github.com/mongodb/mongo/commit/57edce7396271531dde4499458b22c9cde1f03d4

Comment by Sulabh Mahajan [ 02/Apr/19 ]

All slow operation changes need to go to v4.0

Comment by Githook User [ 13/Feb/19 ]

Author:

{'name': 'nehakhatri5', 'email': 'neha.khatri@mongodb.com', 'username': 'nehakhatri5'}

Message: SERVER-39488 Look for storage stats in the find command's profiled entry.

The find command will always have the storage stats because the
test has created a collection with btree spanning multiple pages. Scanning
this collection after a server restart will trigger read from the disk
and have the disk read stats.
Branch: master
https://github.com/mongodb/mongo/commit/6125b5fb078a316854f0299b96b7d16eacb944de

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