Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DataHammer
Starting Member
3 Posts |
 Posted - 2013-02-01 : 11:29:02
|
| This is an interesting one. Windows 2008r2SP1 EESQL 2008r2SP2CU1 EEWe have installed Cluster Service Update KB 2710487, which is supposed to fix inexplicable Cluster Service crashes with error 1359."The cluster service encountered an unexpected problem and will be shut down. The error code was '1359'"The problem is that the Update increases CPU consumption a great deal. We've identified some interesting behavior:• Install the patch on one Node, reboot the Node. CPU is normal (0) until you move a cluster group to that node• With each Cluster Group Move a 1.25% increase in CPU is added to the Node, and it persists. Forever. Note that these are dedicated Nodes, and SQL Groups are complete inactive (no users, no databases)• This CPU increase persists even after all Cluster Groups are moved off the Node• 3 processes clearly account for the total CPU increase. When comparing these processes to non-updated hosts we found each of their CPU usage has clearly increased, and each are in constant use. On non-patched hosts all 3 processes have little CPU usage, and are in use infrequently. Here's some metrics:PROCESSES ON A NON-UPDATED NODEProcess CPU Frequency------------------ --------- ------------------------------Clussvc 1 Frequent but not steadylssas 0 infrequentWmiprvse 0 infrequent --- 1 Total Avg CPU PROCESSES ON AN UPDATED NODEProcess CPU Frequency------------------ --------- ------------------------------Clussvc 10 Constantlssas 2 ConstantWmiprvse 1 Constant --- 13 Total Avg CPU • When a workload is placed on the Cluster Node, CPU consumption of these 3 processes increases. The worst we're seeing is a 15% CPU increase on each node, where each Node is hosting 4 active SQL Groups. The inactive Node in this Cluster has a steady 5% CPU load. It is hosting 4 SQL Groups with activity. • CPU usage patterns by these 3 processes on Updated Nodes are the same regardless of Node CPU and Memory resourcesMS tried to argue that this was not a significant increase... riiiiiiiiight. So after days and days of data collection and arguing with support, they've finally agreed this is a bug, and it will be fixed. Unfortunately this is as far as we've gotten. We have no root cause, or time frame for the fix. We badly need to fix this 1359 error, but we can't afford a 15% increase in CPU. One thing we've found is that Clusters with Updated Nodes have overly verbose Heartbeat chatter:Cluster Update Status Packet/Sec--------------------------- ----------------0 of 5 nodes Updated 25721 of 2 nodes Updated 57952 of 2 nodes Updated 120084 of 4 nodes Updated 18865Have any of you seen this issue or have thoughts on HB chattiness being a root cause for CPU load increase? |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2013-02-06 : 12:54:51
|
| We installed CU3 for SP2 (http://support.microsoft.com/kb/2754552).Fixed the event log chatter, and a non-yielding scheduler thread issue.Not having the CPU issues you are seeing. |
 |
|
|
DataHammer
Starting Member
3 Posts |
Posted - 2013-02-06 : 13:46:23
|
| Thanks for the reply Russell, I will give that KB the once over. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2013-02-06 : 17:07:03
|
| You're welcome. Hope it helps. |
|
|
|
|
|
|
|
|
Cluster Update KB2710487 CPU Increase