ID | IEP-94 |
Author | |
Sponsor | |
Created | |
Status | DRAFT |
Ignitevisorcmd requires a daemon node to be started. We would like to completely remove the concept of a daemon node from the Ignite codebase in the near future..
Ignitevisorcmd is written in scala, we have problems testing, maintaining and improving its codebase.
Users may be confused that we have several tools that do the same things (ignitevisorcmd and control script).
We need to move the missing ignitevisorcmd functionality to the control script.
Function name | Description | implemented in control script | Need move to control script |
---|---|---|---|
Ack command | no | no | |
List caches | yes | no | |
List system caches | no | ? | |
Cache reset lost partitions | yes | no | |
Display lost partitions | no | ||
Cache scan | no | yes | |
Cache clear | no | no | |
Cache reset metrics | yes | no | |
Cache drop | yes | no | |
Node configuration | yes | ||
Print discovery events | |||
Print events history (EventStorageSpi) | |||
Metrics monitoring (alert) | no | ||
Garbage collection runner | no | ||
Deploy manager | no | ||
Kill/restart/start node | |||
Node statistics | |||
Ping node | yes | no | |
Topology | yes | no | |
Run visualVM | no |
// Describe project risks, such as API or binary compatibility issues, major protocol changes, etc.
// Links to discussions on the devlist, if applicable.
// Links to various reference documents, if applicable.
// Links or report with relevant JIRA tickets.