-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xSQLServerMaxDop: Should Be Cluster Aware #882
Comments
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. |
To resolve this issue, a parameter called The The I put together this gist as a guide to updating the resource. Also, see the xSQLServerAlwaysOnAvailabilityGroup resource for a completed example. |
I will work on this one. |
@PaulFeaser Great, thank you! Labeled as in progress. |
- Changes to xSQLServerMaxDop - 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 #882).
Details of the scenario you tried and the problem that is occurring:
When the xSQLServerMaxDop resource is applied to all of the nodes in a Failover Cluster Instance (FCI), all of the nodes will connect to the instance and ensure the desired state is true even if the node is not currently hosting the instance.
The DSC configuration that is using the resource (as detailed as possible):
When the following configuration is applied to two or more nodes in a 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: