...
| Info |
|---|
Example - pico -view The following displays the status for all pico instances in the system. | Code Block |
|---|
| mzsh <username>/<password> pico -view |
Output: | Code Block |
|---|
| Pico Start Memory Response Error Marked For
Name Time (Used, Commited, Max) Time (ms) Status Shutdown
ec1 (ip:port) <time> 1.1, 24.2, 27.6 1 OK
ec2 (ip:port) <time> 1.2, 23.3, 28.7 1 OK
MZSH:45881 (ip:port) <time> 5.9, 15.5, 47.5 2 OK
Platform (ip:port) <time> 8.2, 20.0, 27.6 2 OK |
The Memory column is a comma-separated list of Used, Committed, and Maximum memory, and Response Time is measured in milliseconds. If Error Status indicates "Error", an OutOfMemoryError has occurred and additional information will be included in the output. For example, in case of an OutOfMemoryError on the Platform, the following could be shown: | Code Block |
|---|
| Platform: Mon Jan 23 09:59:47 CET 2012 OutOfMemoryError on platform at platform-e6410.
See log/platform.log for more information |
OutOfMemoryError is further described in Out of Memory Info in System Log. https://infozone.atlassian.net/wiki/x/hCc0D If Error Status indicates "Connection failure", an RCP error has occurred. The following command displays the status of the pico instance named ec1. | Code Block |
|---|
| mzsh <username>/<password> pico -view ec1 |
Output: | Code Block |
|---|
| Pico Name: ec1 (10.0.0.8:37197)
OS: LINUX
OS Version: 2.6.38-11-generic-pae
Architecture: I386
Processors: 8
Java Version: 1.8.0_121
Loaded Classes: 2854 |
|
...
Use pico -mark_for_shutdown to signal to the Platform that an EC is scheduled to be shut down. As a result, the Platform will not assign workflows to the EC/ECSA.
| Info |
|---|
Example - pico -mark_for_shutdown The following command signals that the EC named EC1 should not be assigned workflows | Code Block |
|---|
mzsh <username>/<password> pico -mark_for_shutdown ec1 localhost true |
Output: |
...
