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.

Sign up for GitHub

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

Jump to bottom

Investigate getting rid of all timed operations #21

Open
kkrugler opened this issue Oct 8, 2018 · 0 comments
Open

Investigate getting rid of all timed operations #21

kkrugler opened this issue Oct 8, 2018 · 0 comments
Assignees
@kkrugler

Comments

@kkrugler
Copy link
Member

kkrugler commented Oct 8, 2018

Currently we have timed operations for...

  1. How long to have source run before it terminates.
  2. How long iteration can be quiet before it terminates.
  3. How long we delay between each feature, to avoid deadlock.

If we start up a mini cluster and then terminate it when we decide the job is done, we could avoid the first two. The last one relies on limiting in-flight features.
@kkrugler kkrugler self-assigned this Oct 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kkrugler kkrugler

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kkrugler