Bug ID 812373: Data collection after a service is forced to restart

Last Modified: Jun 30, 2021

Bug Tracker

Affected Product:  See more info
BIG-IQ System User Interface(all modules)

Known Affected Versions:
6.1.0, 7.0.0, 7.0.0.1, 7.0.0.2, 7.1.0, 7.1.0.1, 7.1.0.2, 7.1.0.3, 7.1.6, 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2, 7.1.8, 7.1.8.1, 7.1.8.2, 7.1.8.3, 7.1.8.4, 7.1.8.5, 7.1.9, 7.1.9.7, 7.1.9.8, 7.1.9.9

Opened: Aug 05, 2019
Severity: 3-Major

Symptoms

Data collection cluster fails to collect data or respond to queries causing issues with event collection and visualization.

Impact

Data collection and visualization becomes inoperative.

Conditions

If one or more of the data collection devices becomes unreachable from the console or other data collection devices, due to networking, restarting, or other environmental issues, it is possible that the cluster can become unhealthy and unable to respond to inbound data or query requests. Issues like excessive memory usage or network instability can trigger these erratic changes.

Workaround

If data backups (snapshots) or data loss is acceptable then: -- Stop elasticsearch process on console and each data collection device (“bigstart stop elasticsearch”) -- Delete the contents of /var/config/rest/elasticsearch/data directory on the devices rm -rf /var/config/rest/elasticsearch/data/* -- Restart elasticsearch process on console and each data collection device (“bigstart start elasticsearch”)

Fix Information

None

Behavior Change