- Pivotal Greenplum 4.2.x
- OS All Supported Versions
When you attempt to check the status of the standby master in a Greenplum instance using " gpstate -f ", you see the following error message:
Summary state : Not synchronized Detail state : Standby master too far behind
This means that the standby of the master was down for quite some time now and when you place the request to re-sync, the master has gone way ahead and now the files need to be re-synced as the standby is no longer available.
In order to fix this, you need to resynchronize the standby as shown below:
gpinitstandby -M fast -n
In some cases, if the above command could not fix the issue, then you may need to remove the standby and add it again. Below are the steps for the same:
1) To remove the standby run
gpinitstandby -M fast -r
2) And then reinitialize the standby again using the command below
gpinitstandby -M fast -s smdw
You will be requiring a little bit of downtime for Greenplum versions 4.2.x when this is carried out since Master mirroring is not incremental and needs full a copy during resynchronization. To achieve this, gpinitstandby will shut down and start the database again as a part of the process. There are some improvements in master mirroring for Greenplum versions 4.3.x and this resynchronization or initialization is online now which does not need downtime.