This article applies to BoKS Manager 6.7.0, 6.7.1 and 7.0.0.
At Boot or when boks_servm on a Replica has not received any database updates for some time, it sends a message to the Master asking it to check the Replica's status and add it to the list of active Replicas if not present. This message was batched.
If there were already many batched messages waiting in the queue to be sent to the Master, it would take a long time for this message to reach the Master, causing the Replica database not to be updated if it was not already marked as OK in the 'boksdiag list' output.
Resolution / Workaround
Apply hotfix HFBM-0131 (BoKS 6.7) or HFBM-0132 (BoKS 7.0), available for download from the HelpSystems Community Portal.
This message has been changed to be sent as a volatile batched message, and boks_bridge has been updated to let these types of messages have higher priority than normal batched messages so it is sent as soon as possible even if there are normal batched messages waiting to be sent.
Version 2 of HFBM-0131:
Version 2 fixes the following issue found in the first version of the hotfix: In certain cases, some messages from the Replica to the Master were left in the queue and not sent until BoKS was restarted.
Still have questions? We can help. Submit a case to Technical Support.