Skip to content
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

Run tasks indefinitely #318

Closed
danielmitterdorfer opened this issue Sep 12, 2017 · 0 comments
Closed

Run tasks indefinitely #318

danielmitterdorfer opened this issue Sep 12, 2017 · 0 comments
Labels
bug Something's wrong :Load Driver Changes that affect the core of the load driver such as scheduling, the measurement approach etc. :Track Management New operations, changes in the track format, track download changes and the like
Milestone

Comments

@danielmitterdorfer
Copy link
Member

Consider the following schedule:

{
  "parallel": {
    "completed-by": "index",
    "warmup-time-period": 240,
    "tasks": [
      {
        "operation": "index",
        "clients": 8
      },
      {
        "operation": "term",
        "clients": 1,
        "target-throughput": 20
      }
    ]
  }
}

Expected behavior: We want to run a term query in parallel with indexing. However, we don't really care how often the term query runs. It should just run as long as we're indexing and then terminate.
Actual behavior: Rally runs the query just once and does not show any results because this sample is finished within the warmup time period of 240 seconds.

We should fix this by assuming that the term query should be run indefinitely. Note that with the new behavior we rely that it is only used in schedules like the above. For example, the following schedule will never terminate:

{
  "operation": "term",
  "clients": 1,
  "warmup-time-period": 240,
  "target-throughput": 20
}

If we want it to terminate, we need to specify a time-period.

For the time being we will not implement any validation for these cases.

@danielmitterdorfer danielmitterdorfer added :Load Driver Changes that affect the core of the load driver such as scheduling, the measurement approach etc. :Track Management New operations, changes in the track format, track download changes and the like bug Something's wrong labels Sep 12, 2017
@danielmitterdorfer danielmitterdorfer added this to the 0.7.2 milestone Sep 12, 2017
danielmitterdorfer added a commit that referenced this issue Sep 15, 2017
With this commit we upgrade to thespian 3.8.0 and replace a workaround
to use multiple timers per actor with the now available proper solution.

Closes #318
danielmitterdorfer added a commit that referenced this issue Oct 10, 2017
With this commit we upgrade to thespian 3.8.0 and replace a workaround
to use multiple timers per actor with the now available proper solution.

Closes #318
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something's wrong :Load Driver Changes that affect the core of the load driver such as scheduling, the measurement approach etc. :Track Management New operations, changes in the track format, track download changes and the like
Projects
None yet
Development

No branches or pull requests

1 participant