opensearch-project/opensearch-benchmark-workloads

[BUG] Issue in Eventdata / transform test procedure

Open

#143 opened on Nov 21, 2023

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Python (137 forks)auto 404
Low Prioritybuggood first issue

Repository metrics

Stars
 (33 stars)
PR merge metrics
 (PR metrics pending)

Description

What is the bug?

Running "transform" test procedure of "eventdata" workload fails during delete-transform-group-by-terms step :

Running delete-index [100% done] Running create-index [100% done] Running check-cluster-health [100% done] Running index-append [100% done] Running force-merge [100% done] Running wait-until-merges-finish [100% done] Running delete-transform-group-by-terms [ 0% done] Running delete-transform-group-by-terms [ 0% done] [ERROR] Cannot execute-test. Error in load generator [0] Cannot run task [delete-transform-group-by-terms]: 'request_start'

How can one reproduce the bug?

opensearch-benchmark execute-test --workload eventdata --test-procedure=transform --pipeline=benchmark-only --target-host=http://target-host:9200 --on-error="abort"

What is the expected behavior?

Get all steps running fine

What is your host/environment?

opensearch-benchmark 1.1.0 running in docker (opensearchproject/opensearch-benchmark:latest) opensearch cluster (host target) version is 2.10.0 running in virtual machines

Contributor guide

Research direction
Examine the 'eventdata' workload definition and trace the 'delete transform group by terms' task to find where 'request start' is expected but missing. Check the load generator code for how tasks are executed.
Tech stack
python
Domain
testingdevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65