Make horizontal data generation more robust
After investigation of customer's logs in #440 (closed), we identified what should be done to make data generation more robust #440 (comment 564723054).
- Pin groups thread iterations to pool size
- Add a wait after
change_env_settings
call so that the change is propagated- Was able to replicate scheduled group deletion problem that we see in the logs. Turned out that the delete request was called too quickly after
disable_soft_delete_settings
, so that the env setting hasn't changed yet. Adding a wait resolved the issue.
- Was able to replicate scheduled group deletion problem that we see in the logs. Turned out that the delete request was called too quickly after
- Use subgroup number as a base for child projects.
- Previously we could have
gpt-subgroup-1
with projectsgpt-project-(20...25)
. Now we use subgroup number for child projects name, so that we will always havegpt-subgroup-1
withgpt-project-(1...5)
.
- Previously we could have
Closes #440 (closed)