-
Notifications
You must be signed in to change notification settings - Fork 28
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
Introduce ChaosEngineering for ShardingSphere #32
Comments
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. |
Currently we plan to support two types of chaos for ShardingSphere:
|
Recent thoughts on this, propose a new CRD called ShardingSphereChaos that contains two different kinds of Chaos:
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. |
As a critical components for any production use, ShardingSphere plays a very important role which have a high level availability requirements.
The text was updated successfully, but these errors were encountered: