-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines
-
StorEng - Defined Pipeline, 2023-11-28 - Anthill Tiger
-
5
WT::compact skips compaction if the data size is too small
"skipping because the file size must be greater than 1MB"
[js_test:index_version_autoupgrade] d50050| {"t":{"$date":"2023-04-06T20:06:52.860+00:00"},"s":"I", "c":"WTCMPCT", "id":22430, "ctx":"conn1","msg":"WiredTiger message","attr":{"message":{"ts_sec":1680811612,"ts_usec":860738,"thread":"11893:0x7f3546e11700","session_dhandle_name":"file:collection-15--5349796768648330457.wt","session_name":"WT_SESSION.compact","category":"WT_VERB_COMPACT","category_id":7,"verbose_level":"INFO","verbose_level_id":0,"msg":"collection-15--5349796768648330457.wt: skipping because the file size must be greater than 1MB: 4096B."}}}
MDB layer JS tests calling the compact command aren't actually testing compaction because compaction is skipped due to too little data. For reference this is the WT::compact code.
This is the list of effected tests:
jstests/noPassthrough/index_version_autoupgrade.js.
jstests/replsets/read_committed_with_catalog_changes.js
jstests/concurrency/fsm_workloads/compact.js
jstests/concurrency/fsm_workloads/compact_while_creating_indexes.js
There are other tests call the MDB compact command, but the intent in those tests are things like auth, allowed to run on a secondary, view namespace handling, etc.
- related to
-
SERVER-79869 The WiredTiger event handler is not used correctly when calling compact
- Closed
-
SERVER-70201 Make compact killable
- Closed