|
Problem IT38594
|
Status: Closed |
DOC: SEC_APPLY_POLLTIME SHOULD NOT BE SET TO A VALUE GREATER THAN 100 ON SECONDARY SERVERS WITHOUT SIGNIFICANT LOAD TESTING
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
The value of SEC_APPLY_POLLTIME, also considering
OFF_RECVRY_THREADS and Number of CPU VPs, should not be set
higher than 100, even though the DOCUMENTATION and onconfig.std
recommend this for systems with more than 16 CPU VPs.
If OFF_RECVRY_THREADS is set to higher than the number of CPU
VPs, or even a significant proportion, together with
SEC_APPLY_POLLTIME set to 1000, then the Logical Log Apply may
thrash mreplay threads causing potentially significant
performance degradation of Logical Log application on Secondary
Servers. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Documentation prior to 14.10.xC8 release. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
****************************************************************
To set non zero value for SEC_APPLY_POLLTIME, OFF_RECVRY_THREADS
onconfig value must be less than CPU VPs configured for the
database server. |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Documentation prior to 14.10.xC8 release. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
****************************************************************
To set non zero value for SEC_APPLY_POLLTIME, OFF_RECVRY_THREADS
onconfig value must be less than CPU VPs configured for the
database server. |
| Comment |
Fixed in Informix Server 14.10.xC8. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.10.2021
08.04.2022
08.04.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
