diff options
| author | nehakhatri5 <neha.khatri@mongodb.com> | 2019-02-11 16:03:40 +1100 |
|---|---|---|
| committer | nehakhatri5 <neha.khatri@mongodb.com> | 2019-02-13 14:22:29 +1100 |
| commit | 6125b5fb078a316854f0299b96b7d16eacb944de (patch) | |
| tree | e0f040d6d91094b008959757ddbd9a085d2c5f46 | |
| parent | 613454eb99abe25682f9a50d93ee04e7e90ba314 (diff) | |
| download | mongo-6125b5fb078a316854f0299b96b7d16eacb944de.tar.gz | |
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.
| -rw-r--r-- | jstests/noPassthrough/wt_operation_stats.js | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/jstests/noPassthrough/wt_operation_stats.js b/jstests/noPassthrough/wt_operation_stats.js index bee9fd9eded..cccdcb59547 100644 --- a/jstests/noPassthrough/wt_operation_stats.js +++ b/jstests/noPassthrough/wt_operation_stats.js @@ -77,7 +77,8 @@ } checkLogStats(); - let profileObj = getLatestProfilerEntry(testDB); + // Look for the storage statistics in the profiled output of the find command. + let profileObj = getLatestProfilerEntry(testDB, {op: "query", ns: "wt_op_stat.foo"}); checkSystemProfileStats(profileObj, "bytesRead"); MongoRunner.stopMongod(conn); |