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

Hypothesis: Reaching the maxMessageLimit in an workflow instance will not break the partition #33

Open
ChrisKujawa opened this issue Jul 16, 2020 · 1 comment
Open

Hypothesis: Reaching the maxMessageLimit in an workflow instance will not break the partition #33

ChrisKujawa opened this issue Jul 16, 2020 · 1 comment
Labels
Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Performability This issue will contribute to build up confidence in performability. Hypothesis A thing which worries us and is ready for exploration. Impact: Medium The issue has an medium impact on the system. Likelihood: High The likelihood of this issue is really high!

Comments

@ChrisKujawa
Copy link
Member

Hypothesis

We believe that even when a workflow instance reached the maxMessageLimit, due to multi instance, call activity or task output mapping or otherthing it will not block the complete processing of the partition. Only the related instance should be blacklisted.
@ChrisKujawa ChrisKujawa added Hypothesis A thing which worries us and is ready for exploration. Impact: Medium The issue has an medium impact on the system. Likelihood: High The likelihood of this issue is really high! Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Performability This issue will contribute to build up confidence in performability. labels Jul 16, 2020
@ChrisKujawa
Copy link
Member Author

See https://github.com/zeebe-io/zeebe-chaos/blob/master/chaos-days/2020-07-16/README.md

@ChrisKujawa ChrisKujawa mentioned this issue Jun 8, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Performability This issue will contribute to build up confidence in performability. Hypothesis A thing which worries us and is ready for exploration. Impact: Medium The issue has an medium impact on the system. Likelihood: High The likelihood of this issue is really high!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ChrisKujawa