Network related vertica outage

Document ID : KB000047179
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction:

This knowledge doc will show what to look for in the vertica.log if there are network related issues

 

Question: 

How can we determine if the cause of a vertica outage was network related? 

 

Environment: 

2.x 

 

Answer:  

The following types of messages are seen in the vertica.log if there were network related problems

 

2016-01-18 10:35:29.903 Spread Client:0x1238ac00 [Comms] <INFO> Saw membership message 8192 on V:drdata

2016-01-18 10:35:29.903 Spread Client:0x1238ac00 [Comms] <INFO> Saw transitional message; watch for lost daemons

2016-01-18 10:35:29.904 Spread Client:0x1238ac00 [Comms] <INFO> Saw membership message 8192 on Vertica:all

2016-01-18 10:35:29.904 Spread Client:0x1238ac00 [Comms] <INFO> Saw transitional message; watch for lost daemons

2016-01-18 10:35:29.904 Spread Client:0x1238ac00 [Comms] <INFO> Saw membership message 8192 on Vertica:join

2016-01-18 10:35:29.904 Spread Client:0x1238ac00 [Comms] <INFO> Saw transitional message; watch for lost daemons

2016-01-18 10:35:29.904 Spread Client:0x1238ac00 [Comms] <INFO> Saw membership message 6144 on V:drdata

2016-01-18 10:35:29.904 Spread Client:0x1238ac00 [Comms] <INFO> NETWORK change with 1 VS sets

2016-01-18 10:35:29.904 Spread Client:0x1238ac00 [Comms] <INFO> VS set #0 (mine) has 1 members (offset=36)

2016-01-18 10:35:29.904 Spread Client:0x1238ac00 [Comms] <INFO> VS set #0, member 0: #node_a#N172030002090

2016-01-18 10:35:29.904 Spread Client:0x1238ac00 [Comms] <INFO> DB Group changed

 

If network related issues are consistently causing an outage then the vertica tools should be utilized to determine what changes if any, would be needed to stabilize the environment

 

Additional Information:

For information on CAPM's vertica tools please review the following tech doc: TEC1540586