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

Introduce ChaosEngineering for ShardingSphere #32

Open
mlycore opened this issue Aug 22, 2022 · 4 comments
Open

Introduce ChaosEngineering for ShardingSphere #32

mlycore opened this issue Aug 22, 2022 · 4 comments
Assignees
@mlycore
Labels
in: chaos modules of shardingsphere chaos type: enhancement New feature or request type: help wanted Extra attention is needed

Comments

@mlycore
Copy link
Contributor

mlycore commented Aug 22, 2022

As a critical components for any production use, ShardingSphere plays a very important role which have a high level availability requirements.
@mlycore mlycore added type: enhancement New feature or request type: help wanted Extra attention is needed in: chaos modules of shardingsphere chaos labels Oct 7, 2022
@mlycore
Copy link
Contributor Author

mlycore commented Dec 30, 2022

At first we plan to have the DatabaseChaos, providing some tests on high availability of ShardingSphere. DatabaseChaos is currently a CRD of DatabaseMesh supporting AWS RDS Instance rebooting and AWS RDS Cluster automatically failover.

@mlycore mlycore self-assigned this Dec 30, 2022
@mlycore
Copy link
Contributor Author

mlycore commented Feb 22, 2023

Currently we plan to support two types of chaos for ShardingSphere:

  • Infra: like Kubernetes and AWS chaos
  • JVM: general JVM chaos

@mlycore mlycore assigned mlycore and unassigned mlycore Mar 1, 2023
@mlycore
Copy link
Contributor Author

mlycore commented Mar 9, 2023 •
edited

Here are the issues:

@mlycore
Copy link
Contributor Author

mlycore commented Mar 16, 2023

Recent thoughts on this, propose a new CRD called ShardingSphereChaos that contains two different kinds of Chaos:

  • General Chaos: including kubernetes, network, disk, time, etc.
  • JVMChaos: including byteman/bytebuddy scripts.

We have to specify the detail of one Chaos, the execution requirement, the explosive radius, the load generator, the observed result and its regarding quality gate. Then the chaos would be a full lifecycle management.

This was referenced Mar 16, 2023
Closed
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mlycore mlycore

Labels
in: chaos modules of shardingsphere chaos type: enhancement New feature or request type: help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mlycore