|
Problem IT37646
|
Status: Closed |
RSS_FLOW_CONTROL ALWAYS ENABLED EVEN THOUGH SET TO DISABLED
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
When RSS_FLOW_CONTROL is set to -1 (disabled) under 12.10.FC14
onstat -g rss verbose shows RSS_FLOW_CONTROL as enabled with the
effective setting as 0.
This is compounded by the fact that when set to 0 "minimal"
defaults are in place (Start Flow Control at 12 * LOGBUFF / Stop
Flow Control at 11 * LOGBUFF); so a client who DOES NOT WANT
flow control at all (-1) actually gets flow control occurring at
a (relatively) low RSS lag resulting in the PRIMARY stalling due
to flow control.
Does not occur under 12.10.FC13 or 14.10.FC6 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC7. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC15 or 14.10.xC7 (when *
* available). *
**************************************************************** |
| Local Fix: |
A possible mitigation is to set RSS_FLOW_CONTROL to high values:
RSS_FLOW_CONTROL=2048M,1870M |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC7. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC15 or 14.10.xC7 (when *
* available). *
**************************************************************** |
| Comment |
Fixed in Informix Server 12.10.xC15 and 14.10.xC7. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.07.2021
26.08.2021
26.08.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
