YCSB events - continues events are not correctly set

[fgelcer]

looking at the continues events, YCSB events are not doing it right:

2022-02-04 05:05:04.544: (YcsbStressEvent Severity.NORMAL) period_type=not-set event_id=e9db2ade-ecda-452d-b5c8-48cfafd45619: type=start node=Node rolling-upgrade-4-6-centos-loader-node-34ca1b0e-0-1 [35.229.32.16 | 10.142.0.93] (seed: False)
stress_cmd=bin/ycsb run dynamodb -P workloads/workloada -threads 100 -p recordcount=1010020 -p readproportion=0 -p updateproportion=1 -p scanproportion=0 -p insertproportion=0 -p requestdistribution=uniform -p fieldcount=10 -p fieldlength=512 -p operationcount=1010020 -p table=usertable -s  -P /tmp/dynamodb.properties -p maxexecutiontime=22200

2022-02-04 05:21:26.979: (YcsbStressEvent Severity.NORMAL) period_type=not-set event_id=6548fcfe-325a-461b-b3a8-24fe85ff1c88: type=finish node=Node rolling-upgrade-4-6-centos-loader-node-34ca1b0e-0-1 [35.229.32.16 | 10.142.0.93] (seed: False)
stress_cmd=bin/ycsb run dynamodb -P workloads/workloada -threads 100 -p recordcount=1010020 -p readproportion=0 -p updateproportion=1 -p scanproportion=0 -p insertproportion=0 -p requestdistribution=uniform -p fieldcount=10 -p fieldlength=512 -p operationcount=1010020 -p table=usertable -s  -P /tmp/dynamodb.properties -p maxexecutiontime=22200

and in the same test, looking at another event (NodetoolEvent) we see the period_type defined:

2022-02-04 04:53:07.459: (NodetoolEvent Severity.NORMAL) period_type=begin event_id=02165a35-1e88-41fa-8e81-7596e605caad: nodetool_command=repair node=rolling-upgrade-4-6-centos-db-node-34ca1b0e-0-1

2022-02-04 04:53:10.796: (NodetoolEvent Severity.NORMAL) period_type=end event_id=02165a35-1e88-41fa-8e81-7596e605caad duration=3s: nodetool_command=repair node=rolling-upgrade-4-6-centos-db-node-34ca1b0e-0-1

full logs are here:

+----------------------------------------------------------------------------------------------------------------------------------------------+
|                                       Collected logs by test-id: 34ca1b0e-1a1f-4ad6-b4b9-3a365985c6f0                                        |
+-------------+--------------------------------------------------------------------------------------------------------------------------------+
| Cluster set | Link                                                                                                                           |
+-------------+--------------------------------------------------------------------------------------------------------------------------------+
| db-cluster  | https://cloudius-jenkins-test.s3.amazonaws.com/34ca1b0e-1a1f-4ad6-b4b9-3a365985c6f0/20220204_054007/db-cluster-34ca1b0e.tar.gz |
| loader-set  | https://cloudius-jenkins-test.s3.amazonaws.com/34ca1b0e-1a1f-4ad6-b4b9-3a365985c6f0/20220204_054007/loader-set-34ca1b0e.tar.gz |
| sct-runner  | https://cloudius-jenkins-test.s3.amazonaws.com/34ca1b0e-1a1f-4ad6-b4b9-3a365985c6f0/20220204_054007/sct-runner-34ca1b0e.tar.gz |
+-------------+--------------------------------------------------------------------------------------------------------------------------------+

[github-actions[bot]]

This issue is stale because it has been open 2 years with no activity. Remove stale label or comment or this will be closed in 2 days.

[fruch]

This is still relevant, not urgent/critical.

But something can be done as one of early steps into SCT