返回
-
标题
Hostname switches between two SQL Server hosts triggers false DBSS Cluster Failover alarms -
说明
Hostname switches between two SQL Server hosts triggering false DBSS Cluster Failover alarms
Example alarm
Foglight has generated a Warning alarm for AGENTNAME : DBSS - Cluster Failover Rule: DBSS - Cluster FailoverSeverity: Warning
Message: Cluster Failover. The SQL Server cluster group active node has moved from node SERVER1 to node SERVER2 Created on: 2025-01-16T06:11:42-08:00Messages like the following appear in the SQL Server agent log file
2025-01-16 05:11:05.411 INFO [AGENTNAME-lowPriorityPool-2-[DBSS_Host_Group][2025/01/16 05:11:05]] com.quest.qsi.fason.sqlserver.agent.SqlServerAgentData - Physical host name changed from SERVER1 to SERVER2. 2025-01-16 05:45:13.549 INFO [AGENTNAME-lowPriorityPool-2-[DBSS_Maintenance][2025/01/16 05:45:13]] com.quest.qsi.fason.sqlserver.agent.SqlServerAgentData - Physical host name changed from SERVER2 to SERVER1. 2025-01-16 06:01:54.386 INFO [AGENTNAME-lowPriorityPool-1-[DBSS_Maintenance][2025/01/16 06:01:54]] com.quest.qsi.fason.sqlserver.agent.SqlServerAgentData - Physical host name changed from SERVER1 to SERVER2.
-
原因
When two SQL Server agents create a JDBC connection at the same time (multiple threads) the second agent gets the same connection object from the JDBC driver.
-
解决办法
WORKAROUND
Contact Support for hotfix HFIX-530 for this issue. This hotfix is in the form two jar files that will require a restart of the Foglight Agent Manager (FglAM) service.
STATUS
This issue has been logged as HFIX and will be fixed in an upcoming release of the SQL Server cartridge.
-
缺陷ID
HFIX-530