Why did the Data Repository shut down
book
Article ID: 95853
calendar_today
Updated On:
Products
CA Infrastructure Management
CA Performance Management - Usage and Administration
Issue/Introduction
Why did the Data Repository shut down
Environment
CA Performance Management - all versions
Resolution
The Data Repository Nodes will shut down if there are network issues preventing cluster communication
In the <catalog/>/v_drdata_node000#_catalog/vertica.log file look for an entry similar to the following:
2018-05-03 01:09:42.942 Spread Client:7fd7535fe700 [Comms] <INFO> Saw transitional message; watch for lost daemons
2018-05-03 01:09:42.942 Spread Client:7fd7535fe700 [Comms] <INFO> Saw membership message 6144 (0x1800) on V:drdata
2018-05-03 01:09:42.942 Spread Client:7fd7535fe700 [Comms] <INFO> NETWORK change with 1 VS sets
2018-05-03 01:09:42.942 Spread Client:7fd7535fe700 [Comms] <INFO> VS set #0 (mine) has 1 members (offset=36)
2018-05-03 01:09:42.942 Spread Client:7fd7535fe700 [Comms] <INFO> VS set #0, member 0: #node_b#N010255247080
2018-05-03 01:09:42.942 Spread Client:7fd7535fe700 [Comms] <INFO> DB Group changed
This indicates network issues preventing cluster communication with another node which can lead to the database shutting down
Feedback
thumb_up
Yes
thumb_down
No