You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details of the scenario you tried and the problem that is occurring:
When the xSQLServerAlwaysOnAvailabilityGroup resource is applied to all of the nodes in a Failover Cluster Instance (FCI), the nodes will "fight" with each other while trying to create and configure the availability group.
The DSC configuration that is using the resource (as detailed as possible):
The following configuration applied to two or more nodes that host the FCI:
The resource should evaluate if the current node is actively hosting the SQL instance. If it is not hosting the instance, it should write a verbose message stating that it does not own the instance, and then silently exit.
- Changes to xSQLServerAlwaysOnAvailabilityGroup
- Made the resource cluster aware. When ProcessOnlyOnActiveNode is specified,
the resource will only determine if a change is needed if the target node
is the active host of the SQL Server instance (issue #868).
Details of the scenario you tried and the problem that is occurring:
When the xSQLServerAlwaysOnAvailabilityGroup resource is applied to all of the nodes in a Failover Cluster Instance (FCI), the nodes will "fight" with each other while trying to create and configure the availability group.
The DSC configuration that is using the resource (as detailed as possible):
The following configuration applied to two or more nodes that host the FCI:
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Any
What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
Any
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Any
The text was updated successfully, but these errors were encountered: