Problem Note 43570: If one of the peers in a load balanced cluster of 3 or more peers is refreshed or restarted it causes load balancing to behave incorrectly.
Load balancing distributes SAS® sessions across a cluster of servers. You can add or subtract servers to accommodate changes in peak demand. If one of the peers in a load balanced cluster of 3 or more peers is refreshed or restarted it causes load balancing to behave incorrectly.
When one of the peers in the cluster is refreshed or restarted (including the parent peer), it reports incorrect information about who the current parent peer is when it comes back up and connects back to the other peers in the cluster. This causes the newly restarted peer to believe that it is now an erroneous parent peer of the cluster and it therefore remains disconnected from the other peers and will not be able to partipate in load balancing.
The issue can be seen by setting the IOM.LoadBalancing logger set to TRACE. The messages that will appear from the load balancing algorithm will be:
"skipped due to current state (6)".
This would be a valid message if the associated peers were not running.
Operating System and Release Information
SAS System | SAS Integration Technologies | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows XP 64-bit Edition | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft® Windows® for x64 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2003 for x64 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2008 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows Server 2008 for x64 | 9.2 TS2M3 | 9.3 TS1M2 |
Microsoft Windows XP Professional | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Enterprise 32 bit | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Enterprise x64 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Home Premium 32 bit | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Home Premium x64 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Professional 32 bit | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Professional x64 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Ultimate 32 bit | 9.2 TS2M3 | 9.3 TS1M2 |
Windows 7 Ultimate x64 | 9.2 TS2M3 | 9.3 TS1M2 |
Windows Vista | 9.2 TS2M3 | 9.3 TS1M2 |
Windows Vista for x64 | 9.2 TS2M3 | 9.3 TS1M2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
If one of the peers in a load balanced cluster containing 3 or more peers is restarted or refreshed it is returning erroneous information about who the current parent peer is causing connections to be rejected.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2012-01-24 13:35:14 |
Date Created: | 2011-06-21 12:58:11 |