-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
datagenrun in autopilot-script stops data generation after a few seconds without error #758
Comments
Yes, what is happening here is that the main thread is starting the worker threads running and then falling off the end, causing them to stop. It needs the |
Thank you, that works. Unfortunately keepalive is not documented. I'm still using waittocomplete in other scripts. |
I was too early with my reply. It works half-way, command stopped after around generating ~63GB of data. |
Hi, yes it is all in the documentation so If you run them you should get message that they are deprecated:
The replacement of keepalive is also documented: https://www.hammerdb.com/docs/ch09s03.html Note that the runtimer and waittocomplete parameters have been deprecated from v4.6. For this reason an additional configuration parameter of keepalive_margin with a default value of 10 seconds increasing to 60 seconds from v4.10 has been added to generic.xml in the commandline section to modify the additional time that HammerDB will wait after completion before terminating the workload. This can be useful if for example gathering timing data for event driven scaling workloads with a large number of asynchronous clients. So now it is automated it is controlled by the parameter generic parameter keepalive_margin to determine how long it will wait for eg the following changes the default 1 minute (from v4.10) to 20 minutes:
|
Thank you, so I actually have to know in advance the maximum time to wait ? I checked my scrips and actually I use the following for tests which I don't know when they will end: global complete Is this still a good practice ? |
No, you don't need that for the current releases, there are examples in the scripts directory for all databases that can be run with tcl or python e.g. These are the best templates for what work.
also there are shell and poweshell scripts here that will do a build, check, run, delete and report with one command.
|
Thank you, I'll adjust my scripts. |
waittocomplete is now the hidden command _waittocomplete and is called automatically by build schema and TPROC-H runs. This waits until vucomplete returns true, so in the rare event a virtual user does not complete it can wait forever. keepalive is more for vurun where it waits for the rampup + test duration + keepalive margin and will kill any virtual users that exceed this time. |
ok, thank you. |
Guidance
Bug reports are for when HammerDB is not behaving as expected.
Bug reports should not be submitted for help in understanding database performance related questions.
General questions on database performance or HammerDB usability should be submitted under Discussions.
Describe the bug
Running a script to generate data using datagenrun with hammerdbcli auto stops a few seconds after start without any error or information.
The same lines in hammerdbcli finish successfully
To Reproduce
Steps to reproduce the behavior:
dbset bm TPROC-C
dgset warehouse 600
dgset vu 10
dgset directory "/SPACE/TPCC_DATA/600WH"
print datagen
datagenrun
Vuser 11:Opened File /SPACE/TPCC_DATA/600WH/order_line_10.tbl
Timestamp 11 @ Fri Sep 27 04:59:08 PDT 2024
Vuser 11:Generating Warehouse
Timestamp 11 @ Fri Sep 27 04:59:08 PDT 2024
Vuser 11:Generating Stock Wid=541
Expected behavior
Expected to behave the same way as other scripts using auto
Screenshots
If applicable, add screenshots to help explain your problem.
HammerDB Version (please complete the following information):
HammerDB Interface (please complete the following information):
Operating System (please complete the following information):
Database Server (please complete the following information):
Database Client (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: