I do not recommend that you set the SDS node updatable
onstat -g ckp
You may see checkpoints triggered by IPL or HA
I try to set it as follows:
LOG_ INDEX_ BUILDS=0
DRIDXAUTO=0
I have many SDS clusters. Some SDS cluster checkpoints are short, but some are still long.
Therefore, my real practice is that if the checkpoint time cannot be shortened, I will close the SDS node.
In addition, can you tell me the version of IDS?
------------------------------
ZhiWei Cui
GBASE
------------------------------
Original Message:
Sent: Thu January 06, 2022 05:01 AM
From: SangGyu Jeong
Subject: SDS TIMEOUT issue
Hello All,
Every 1 or 2 months, SDS Secondary server loses connection due to sds timeout.
Checkpoints take 99 seconds to as long as 347 seconds in some cases.
Customers say it's not a network issue.
Could it be solved by increasing the sds timeout value?
Below are some of the error messages from the primary and secondary servers at the time the problem occurred.
** Primary Server online.log12/11/21 06:56:49 Requesting SDS node topas_sec to shutdown due to SDS cycle timeout12/11/21 06:56:50 Checkpoint Completed: duration was 187 seconds.** SDS Secondary online.log12/11/21 06:51:09 The SMX connection between high availability servers was closed because thepeer server was unresponsive for the timeout period (60 seconds times thenumber of retries).12/11/21 06:51:11 Updates from secondary currently not allowed...12/11/21 09:56:38 Encountered problem processing update on secondary : Cannot create new proxy transaction
Or would adjusting the SMX_NUMPIPES or UPDATABLE_SECONDARY parameters work?
The current VPCLASS and UPDATABLE_SECONDARY parameter settings are as follows.
VPCLASS cpu,num=27,noage
UPDATABLE_SECONDARY is 18
------------------------------
SangGyu Jeong
Software Engineer
Infrasoft
Seoul Korea, Republic of
------------------------------
#Informix