-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
When investigating SERVER-56842, I found a segmentation fault related to the use of the operation tracking feature.
It can be easily reproduced by enabling the feature through the reconfiguration API, i.e:
diff --git a/test/suite/test_reconfig01.py b/test/suite/test_reconfig01.py
index 9a683252b..f9212eec0 100644
--- a/test/suite/test_reconfig01.py
+++ b/test/suite/test_reconfig01.py
@@ -34,6 +34,10 @@ from wtdataset import SimpleDataSet
# Smoke-test the connection reconfiguration operations.
class test_reconfig01(wttest.WiredTigerTestCase):
+ def test_reconfig_op_tracking(self):
+ # Change the optrack
+ self.conn.reconfigure("operation_tracking=(enabled=true,path=.)")
+
def test_reconfig_shared_cache(self):
self.conn.reconfigure("shared_cache=(name=pool,size=300M)")
It seems that there is no test dealing with the operation tracking feature. If this feature is still used/maintained, tests should be added too if possible.