IBM Streams 4.2
Unhealthy elements
You must investigate any element that is colored as unhealthy. Unhealthy elements indicate problems in your applications.
When there are unhealthy elements, verify the following things:
- Are other jobs healthy? If none of the jobs are healthy there is likely a fundamental problem with your instance. In the Streams Explorer view, check that the management services are running to verify that the instance is still functioning.
- Are other elements unhealthy or only some? Newly submitted jobs might not be fully healthy while they are initializing and waiting for connections to be established. The job can take a few seconds to fully initialize and start.
- Are all the unhealthy elements on the same host? You can use the
highlighting features or the layout options of the instance graph
to verify whether all the unhealthy elements are on the same host.
- Right-click the element and click Highlight Same Host.
- To lay out the graph by host, from the layout options, select Host. This action creates a container for each host and places all the operators for that host in the container. If all the operators in the host container are unhealthy, it is likely that the problem is with the host.
- Check the process ID of the element. Hover over the unhealthy element and in the Deployment Information section, check the PID value. If the value is 0, the processing element is not running.
- Check the connections. If there are broken connections, an operator is marked unhealthy. Broken connections are colored as unhealthy and the line is shown broken. Hover over the stream, and in the Connection and Underlying PE Connection sections, you can view information about the state of the connection.
After you determine the scope of the problem, whether it is limited to a single operator, entire PE, host, or an instance, you can investigate further by getting the log, trace, and console files.