When we onboard a new org/env scope, a zookeeper notification is sent to the postgres-server component which triggers this to initiate the DB calls to add the additional tables.
If for whatever reason this zookeeper notification does not reach the postgres-server component, the scope onboarding is not carried out and won't adds an extra column in the relevant fact table in the postgresql database.
A restart of the postgres-server component typically resolves the issue because during a restart postgres-server reads all information relevant to AX from zookeeper.
While restarting the master node, the write request would fail, As all the write request goes to the master server, and if master is in restart phase the request will go to the standby node. But slave would be not able to process any write request, and will see below exception in pg system.log
"ExceptionUtil.isReadOnlyModeError() : The current query was made against a read-only mode database - classifying this exception as a retriable exception”
So we need to promote the slave to master first, restart master and promote it to master again, so that write request gets process too.
LinkedIn
Twitter
