Critical NSX System Event Code: 400007
Article ID: 338617
Updated On:
Products
VMware NSX Data Center for vSphere
Issue/Introduction
Symptoms:
Critical NSX System Event - 1 events Reindex Operation is initiated on NSX Manager DB.
Severity: Critical Manager:
Defined By: System
Event Tags: System
Event NSX Event Code: 400007
NSX Module: Monitoring Service
Message: Critical NSX System Event for VMware NSX Manager
2019-08-03 00:00:00.618 GST INFO TaskFrameworkExecutor-18 EventServiceImpl:119 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] [SystemEvent] Time:'Sat Aug 03 00:00:00.617 GST 2019', Severity:'Critical', Event Source:'Monitoring Service', Code:'400007', Event Message:'Reindex Operation is initiated on NSX Manager DB.', Module:'Monitoring Service', Universal Object:'false'
2019-08-03 00:00:00.620 GST INFO systemEventsPool-1 VcConnection$1:227 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Invoking ExtensionManager.findExtension on ExtensionManager, operationID=opId-1bd7a-10474179
2019-08-03 00:00:00.891 GST INFO TaskFrameworkExecutor-18 ReIndexTask:101 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Reindexing time taken for index : job_instance_x_last_update_time_idx is 270 millseconds
2019-08-03 00:00:00.892 GST INFO TaskFrameworkExecutor-18 ReIndexTask:76 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] REINDEXING COMPLETE in : 0 seconds
- Alarm is triggered in VRNI:
Critical NSX System Event - 1 events Reindex Operation is initiated on NSX Manager DB.
Severity: Critical Manager:
Defined By: System
Event Tags: System
Event NSX Event Code: 400007
NSX Module: Monitoring Service
Message: Critical NSX System Event for VMware NSX Manager
- In the /logs/management_service/vsm.log file you see log entries similar to:
2019-08-03 00:00:00.618 GST INFO TaskFrameworkExecutor-18 EventServiceImpl:119 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] [SystemEvent] Time:'Sat Aug 03 00:00:00.617 GST 2019', Severity:'Critical', Event Source:'Monitoring Service', Code:'400007', Event Message:'Reindex Operation is initiated on NSX Manager DB.', Module:'Monitoring Service', Universal Object:'false'
2019-08-03 00:00:00.620 GST INFO systemEventsPool-1 VcConnection$1:227 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Invoking ExtensionManager.findExtension on ExtensionManager, operationID=opId-1bd7a-10474179
2019-08-03 00:00:00.891 GST INFO TaskFrameworkExecutor-18 ReIndexTask:101 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Reindexing time taken for index : job_instance_x_last_update_time_idx is 270 millseconds
2019-08-03 00:00:00.892 GST INFO TaskFrameworkExecutor-18 ReIndexTask:76 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] REINDEXING COMPLETE in : 0 seconds
Environment
VMware NSX Data Center for vSphere 6.4.x
Cause
NSX has a housekeeping job which checks if there are any bloated indexes and if it finds some, it will reindex those again.
This housekeeping task raises this System event when it finds any bloated index.(Event code - 400007, Severity - Critical)
Since this is a critical issue which could cause performance issue, event severity is critical.
Once the reindexing is done, it generates a successful event(Event Code - 400008, Severity - Informational).
This housekeeping task raises this System event when it finds any bloated index.(Event code - 400007, Severity - Critical)
Since this is a critical issue which could cause performance issue, event severity is critical.
Once the reindexing is done, it generates a successful event(Event Code - 400008, Severity - Informational).
Resolution
You can ignore these events as NSX is taking care of bloated indexes proactively and preventing performance issues pro-actively that could have come due to these bloated indexes.
Feedback
Yes
No
Powered by
