You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

IDIEP-94
Author
Sponsor
Created

Status

DRAFT


Motivation

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).

Description

We need to move the missing ignitevisorcmd functionality to the control script.

Console visor commands

Function nameDescriptionimplemented in control scriptNeed move to control script
Ack command
nono
List caches
yesno
List system caches
no?
Reset lost partitions
yesno
Display lost partitions
no

Cache scan


noyes
Cache clear
nono
Cache modify
no
Cache reset metrics
yes

no

Cache drop
yesno

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
yesno
Topology
yesno
Run visualVM

no

Risks and Assumptions

// Describe project risks, such as API or binary compatibility issues, major protocol changes, etc.

Discussion Links

// Links to discussions on the devlist, if applicable.

Reference Links

// Links to various reference documents, if applicable.

Tickets

type key summary assignee reporter priority status resolution created updated due

JQL and issue key arguments for this macro require at least one Jira application link to be configured

  • No labels