Skip to content

Issues: zeebe-io/zeebe-chaos

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

39 Open 65 Closed
39 Open 65 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Dependency Dashboard
#554 opened Aug 16, 2024 by renovate bot
10 tasks
Auto deploy process models
#358 opened May 17, 2023 by Zelldon
2
Auto deploy zbchaos worker
#357 opened May 17, 2023 by Zelldon
2
Chaos: Terminating Gateway Stops Workflow Processing Chaos Experiment This issue describes a chaos experiments, which should be created.
#336 opened Mar 21, 2023 by shahamit
5
Chaos: Disconnect zbchaos command fails with runtime error Chaos Experiment This issue describes a chaos experiments, which should be created.
#331 opened Mar 14, 2023 by shahamit
@Zelldon
7
Create shareable execution report for chaos experiments
#330 opened Mar 13, 2023 by shahamit
Zbchaos is printing debug log on default
#323 opened Feb 23, 2023 by Zelldon
Iterate over zbchaos worker error handling
#253 opened Nov 23, 2022 by Zelldon
@Zelldon
Investigate in how we test zbchaos zeebe client interactions
#241 opened Nov 18, 2022 by Zelldon
2
Deploy worker via github action enhancement New feature or request
#125 opened Mar 16, 2022 by Zelldon
Chaos processes produce lots of version numbers enhancement New feature or request Impact: Low The issue has an low impact on the system.
#123 opened Mar 8, 2022 by pihme
5
Make use of operate api
#119 opened Mar 4, 2022 by Zelldon
Hypothesis: Bigger state shouldn't make an impact on Throughput Contribution: Performability This issue will contribute to build up confidence in performability. Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: Medium The issue is not so likely.
#64 opened Oct 27, 2021 by Zelldon
2
Hypothesis: A slow follower doesn't cause performance issues Hypothesis A thing which worries us and is ready for exploration. Impact: Low The issue has an low impact on the system. Likelihood: Low The issue is really unlikely.
#60 opened May 26, 2021 by Zelldon
@deepthidevaki @Zelldon
1
Hypothesis: If a leader has a write error, which is not recoverable, it will step down and another leader should take over. Contribution: Availability This issue will contribute to build up confidence in reliability. Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: Medium The issue is not so likely.
#52 opened Mar 31, 2021 by Zelldon
Hypothesis: Disconnecting Leader and one Follower should not make cluster disruptive Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Reliability This issue will contribute to build up confidence in reliability. Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: High The likelihood of this issue is really high!
#45 opened Nov 17, 2020 by Zelldon
1
Chaos: Run cont. load during experiment Chaos Experiment This issue describes a chaos experiments, which should be created.
#40 opened Oct 13, 2020 by Zelldon
Chaos: Inject latency to broker network Chaos Experiment This issue describes a chaos experiments, which should be created.
#37 opened Sep 28, 2020 by Zelldon
Try wrk to dDOS Zeebe
#36 opened Sep 28, 2020 by Zelldon
2
Try toxiproxi to experiment with Zeebe
#35 opened Sep 28, 2020 by Zelldon
Hypothesis: Reaching the maxMessageLimit in an workflow instance will not break the partition 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!
#33 opened Jul 16, 2020 by Zelldon
1
Hypothesis: We stop accepting commands on reaching disk space Contribution: Availability This issue will contribute to build up confidence in reliability. Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: High The likelihood of this issue is really high! Likelihood: Low The issue is really unlikely.
#32 opened Jul 16, 2020 by Zelldon
Hypothesis:I believe I can start a lot of timers without impacting the general throughput Await Fix 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: Low The issue has an low impact on the system. Likelihood: High The likelihood of this issue is really high!
#31 opened Jul 9, 2020 by Zelldon
1
Hypothesis: Partition one Broker with Gateway doesn't affect other partitions Contribution: Availability This issue will contribute to build up confidence in reliability. 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!
#29 opened Jun 26, 2020 by Zelldon
1
Hypothesis: CPU stress on standalone gateway should not cause harm cluster wise Contribution: Availability This issue will contribute to build up confidence in reliability. Hypothesis A thing which worries us and is ready for exploration. Impact: Low The issue has an low impact on the system. Impact: Medium The issue has an medium impact on the system. Likelihood: Medium The issue is not so likely.
#28 opened Jun 11, 2020 by Zelldon
1
ProTip! Follow long discussions with comments:>50.