The connection configuration for test/csuite/timestamp_abort configures statistics with: "statistics=(fast),statistics_log=(wait=1,json=true)" yet if you look in any WT_TEST.timestamp_abort database directory there never will be any WiredTigerStat.##.## file created or populated with any information.
The child program runs for significantly longer than 1 second (the wait period configured). I looked into why this was.
The reason is that the code in thread_ts_run is calling conn->reconfigure on every iteration through its loop. That is happening every millisecond. The reconfigure code calls conn_stat.c:wt_statlog_create every time and the code in there will destroy and restart the statistics server every time. There is a long comment in that function discussing the decision to always "bounce" the server.
Also the statistics server thread always sleeps its wait period first, before writing out the stats. Therefore, the server never ever gets to run nor create the files nor output any information.
This should be fixed so that we can get meaningful statistics out of timestamp_abort.
- is related to
-
WT-8973 Define semantics of zero timestamp in our APIs
- Closed