Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
Description
Need to adapt the concept of baseline topology (introduced by IEP-4) to Ignite 3.0
Attachments
Issue Links
- duplicates
-
IGNITE-17924 Core distributions zones functionality.
-
- Open
-
1.
|
Need to define/Introduce consistent identifier term |
|
Resolved | Unassigned |
2.
|
Define API of cluster node and move it from network component to the public API |
|
Resolved | Unassigned |
3.
|
Define Ignite Cluster API: cluster/node states, run-levels and their semantics |
|
Resolved | Unassigned |
4.
|
Introduce API in order to manage metastorage group |
|
Resolved | Unassigned |
5.
|
Introduce table space/group concept |
|
Resolved | Unassigned |
6.
|
Create custom policies to adjust list of data nodes (baseline nodes) |
|
Resolved | Unassigned |
7.
|
Partition loss policies. Provide a useful and convenient way to list unavailable/offline partitions |
|
Resolved | Unassigned |
8.
|
Managing baseline via CLI |
|
Resolved | Unassigned |
9.
|
Define minimal list of required metrics to monitor baseline and cluster state |
|
Resolved | Unassigned |
10.
|
Managing metastorage group via CLI |
|
Resolved | Unassigned |
11.
|
Shutdown policy and well-defined scale down protocol |
|
Resolved | Unassigned |