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

New (extra) family trigger semantics #2334

Open
hjoliver opened this issue Jun 29, 2017 · 3 comments
Open

New (extra) family trigger semantics #2334

hjoliver opened this issue Jun 29, 2017 · 3 comments
Milestone

Comments

@hjoliver
Copy link
Member

In addition to FAMILY:fail-all and FAMILY:fail-any (and same for succeed, start, etc.) we should have triggers like "FAMILY:fail-50%-or-more'

#2333 (comment)

We'll need to think hard about a clear and flexible notation here.

@arjclark
Copy link
Contributor

arjclark commented Jul 4, 2017

+1 for this as ensemble sizes continue to grow

@ColemanTom
Copy link
Contributor

Definitely agree on this one, especially for very time critical/emergency systems. I've had to do similar manually from the task level before - polling for 'done' files after a certain time so that the suite could finish up once a reasonable number of ensemble members were done.

@GlennCreighton
Copy link

Upvote this! I ran into a use case where we only wanted to send a critical message when more than X members of an ensemble failed. For now, have scrapped together a workaround whereby each failed member gets the status of the family to check whether the threshold has been reached, and if so, outputs a critical message. Then, the if any of the family members outputs the message, a task is triggered to send an email. It'd be so much nicer to have this construct. Perhaps notation could be something like FAMILY:fail-more-than(X); FAMILY:succeed-more-than(Y)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants