@MXBeanDescription(value="MBean that provides access to grid life-cycle operations.") public interface IgnitionMXBean
Ignition
.Modifier and Type | Method and Description |
---|---|
String |
getState()
Gets state of default grid instance.
|
String |
getState(String name)
Gets state for a given grid instance.
|
void |
restart(boolean cancel)
Restart JVM.
|
boolean |
stop(boolean cancel)
Stops default grid instance.
|
boolean |
stop(String name,
boolean cancel)
Stops named Ignite instance.
|
void |
stopAll(boolean cancel)
Stops all started grids.
|
@MXBeanDescription(value="State of default grid instance.") String getState()
Ignition.state()
@MXBeanDescription(value="Gets state for a given grid instance. Returns state of grid instance with given name.") String getState(@MXBeanParameter(name="name",description="Name of grid instance.") String name)
name
- Name of grid instance.Ignition.state(String)
@MXBeanDescription(value="Stops default grid instance. Return true if default grid instance was indeed stopped, false otherwise (if it was not started).") boolean stop(@MXBeanParameter(name="cancel",description="If true then all jobs currently executing on default grid will be cancelled.") boolean cancel)
cancel
- If true
then all jobs currently executing on
default grid will be cancelled by calling ComputeJob.cancel()
method. Note that just like with Thread.interrupt()
, it is
up to the actual job to exit from execution.true
if default grid instance was indeed stopped,
false
otherwise (if it was not started).Ignition.stop(boolean)
@MXBeanDescription(value="Stops Ignite instance by name. Cancels running jobs if cancel is true. Returns true if named Ignite instance was indeed found and stopped, false otherwise.") boolean stop(@MXBeanParameter(name="name",description="Grid instance name to stop.") String name, @MXBeanParameter(name="cancel",description="Whether or not running jobs should be cancelled.") boolean cancel)
cancel
flag is set to true
then
all jobs currently executing on local node will be interrupted. If
Ignite instance name is null
, then default no-name Ignite instance will be stopped.
It does not wait for the tasks to finish their execution.name
- Ignite instance name. If null
, then default no-name
Ignite instance will be stopped.cancel
- If true
then all jobs currently will be cancelled
by calling ComputeJob.cancel()
method. Note that just like with
Thread.interrupt()
, it is up to the actual job to exit from
execution. If false
, then jobs currently running will not be
canceled. In either case, grid node will wait for completion of all
jobs running on it before stopping.true
if named Ignite instance instance was indeed found and stopped,
false
otherwise (the instance with given name
was
not found).Ignition.stop(String, boolean)
@MXBeanDescription(value="Stops all started grids.") void stopAll(@MXBeanParameter(name="cancel",description="If true then all jobs currently executing on all grids will be cancelled.") boolean cancel)
cancel
flag is set to true
then
all jobs currently executing on local node will be interrupted.
It does not wait for the tasks to finish their execution.
Note: it is usually safer and more appropriate to stop grid instances individually instead of blanket operation. In most cases, the party that started the grid instance should be responsible for stopping it.
cancel
- If true
then all jobs currently executing on
all grids will be cancelled by calling ComputeJob.cancel()
method. Note that just like with Thread.interrupt()
, it is
up to the actual job to exit from executionIgnition.stopAll(boolean)
@MXBeanDescription(value="Restart JVM.") void restart(@MXBeanParameter(name="cancel",description="If true then all jobs currently executing on default grid will be cancelled.") boolean cancel)
cancel
- If true
then all jobs currently executing on
all grids will be cancelled by calling ComputeJob.cancel()
method. Note that just like with Thread.interrupt()
, it is
up to the actual job to exit from executionIgnition.stopAll(boolean)
Follow @ApacheIgnite
Ignite Database and Caching Platform : ver. 2.16.0 Release Date : December 15 2023