Mirror Instance Fails with Error "could not match message header checksum between primary"

Products

• VMware Tanzu Greenplum

Issue/Introduction

Symptoms:

The mirror instance fails with the error "could not match message header checksum between primary". The pg log shows the following:

WARNING","01000","mirror failure, could not match message header checksum between primary 'xxxx' and mirror 'xxxxx', failover requested","identifier 'base/xxxx/xxxx' operation 'open' relation type 'buffer pool' message count 'xxxxx'","run gprecoverseg to re-establish mirror connectivity",,,"mirroring role 'mirror role' mirroring state 'sync' segment state 'up and running' process name(pid) 'mirror consumer writer process(xxxx)' filerep state 'up and running' 

Environment

Cause

There is a possible network issue between the primary instance and the mirror instance.

Resolution

To resolve this issue, execute the following steps: 

1. Check if primary and mirror node has a stable network with command, drop/error packet from netstat -i. If there is a network issue, engage the necessary hardware vendor to fix it.

2. Once the network issue is fixed, run normal gprecoverseg for this mirror instance.