
urika-inventory
The
urika-inventory
command displays the list of analytic services running on each node, as well as the IP
address of each node. For more information, see the
urika-inventory(8)
man page.
Display the list of services running on each Urika-GX node:
#
urika-inventory
urika-rev
The
urika-rev
command displays the version of deployed analytic components on Urika-GX nodes and checks
if a different version of a software component is installed on individual nodes.
For more information, see the
urika-rev(8)
man page.
Display the version components deployed on Urika-GX:
#
urika-rev
urika-state
The
urika-state
command displays the status of Urika-GX analytic services and the service mode the system
is operating in.
For more information, see the
urika-state(8)
man page.
Display status of services:
#
urika-state
Sequence of Execution of Scripts
The urika-state command can be used to view the state services running on Urika-GX. Use this command to
ensure that the following dependencies are met:
●
Before executing the
start -s mesos_master
command, ensure that the ZooKeeper service is up and
running.
●
Before executing the
stop -s mesos_master
command, ensure that the Marathon and Mesos slave
services have already been stopped
●
Before executing the
start -s mesos_slave
command, ensure that the ZooKeeper and Mesos Master
services are up and running.
In addition, it is recommended to stop the Mesos slave service before stopping Marathon via the
urika-stop -
s marathon
command. The
urika-stop -s mesos_slave
command does not have any dependencies,
though any running tasks would be lost. Therefore, it is recommended to ensure that all the existing jobs finish
running before executing the
stop -s mesos_slave
command.
System Management
S3016
53