-
Notifications
You must be signed in to change notification settings - Fork 34
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
Error when running start-workload.sh #60
Comments
Ah.. The
|
This fixes two issues encountered when running start-workload.sh: 1. The README description is incorrect. It should use `=` for config key & value for auditreplay configs. 2. The mapper_class_name value doesn't work - it should look under com.linkedin.dynamometer.workloadgenerator.audit instead of com.linkedin.dynamometer.workloadgenerator
Thanks @xkrogen ! and sorry for the late reply. I've opened a PR to fix a few small issues I encountered while running |
when i running start-workload.sh but failed
|
Hm, yes, this issue is what PR #62 is trying to fix. There's a small issue there.. Let me put together another patch for that |
Hey @sunchao and @hexiangheng , I submitted my own PR for this #84, can you take a look there and see if it looks good? |
Closed by PR #84 |
In the README it says:
However, it seems both
Dauditreplay.input-path
and-Dauditreplay.num-threads
are not valid options. Only valid options are:nn_uri
,start_time_offset
,start_timestamp_ms
, andmapper_class_name
?The text was updated successfully, but these errors were encountered: