Ian Hoang

Hi @lijie123bes, thanks for letting us know that you're experiencing this issue. Based on `NoCompatibleSystemForActor`, it looks like your cluster is undiscoverable and might not be in the same network...

Related META issue https://github.com/opensearch-project/opensearch-benchmark/issues/505

Hi @VinodRakuten, we currently have an [RFC](https://github.com/opensearch-project/opensearch-benchmark/issues/395) for enhancing the `create-workload` feature and mentions this issue and a proposed solution. We'll be implementing these enhancements soon. Feel free to have...

@VinDataR what were the errors that you encountered? Could you provide the exact steps you performed and the exception here? Feel free to redact any private information if sending screenshots...

We plan to work on a faster workaround for extracting corpora and give `create-workload` "restart" options, to pick up from where the timeout occurred. These can be found in the...

Hi @scrawfor99, are you requesting that we just confirm if the above is accurate or if we should also include code-coverage? If the latter, do you have any SOP on...

@scrawfor99 Sorry for the late response, but yes the above is accurate. Currently OSB just uses unit tests and integration testing. @gkamat is currently diving into integration tests to determine...

@heemin32 Have you tried running this same setup with an external cluster (on a separate machine) instead of a local cluster? It may help us pinpoint the issue. You could...

To help community members understand the intentions better and since this is a newly suggested subcommand, we recommend contributors to add an example output from this feature.

@chishui I provided some input on the issue here: https://github.com/opensearch-project/opensearch-benchmark/issues/508#issuecomment-2110807331 Regarding this PR, I'm still concerned over how this subcommand invokes OSB's command line `execeute-test` subcommand. Although it simplifies the...