Secondary index alarms indicate issues that HPE Ezmeral Data Fabric Database might encounter while updating secondary indexes. It is important that you understand what the alarms indicate, and how to resolve the issue causing them.
VOLUME_ALARM_TABLE_INDEX_LAG_HIGH
This alarm displays the paths and names of the source tables for which replication lag is high. High lag times might be caused by these conditions:
dbindexlagsecalarmthresh parameter. See volume modify for more information.This alarm occurs if the JSON table regions cannot connect to any of the internal gateways used to update fields in a secondary index. This might be caused by these conditions:
This alarm occurs when any of the following encoding errors occur during index updates:
You must either correct your underlying data or redefine the index to avoid missing rows. See Troubleshooting Secondary Index Encoding Errors for details about how to identify these errors and possible corrective actions.
You also must manually clear this alarm, even if you drop the index or the table.