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
While deploying/retracting a DSC Pullserver the xDSCWebService resource uses IIS and other server objects which might not react instantly when an operation is issued especially when the server is under heavy load or equipped with limited resources like memory or cpu.
Internal (automatic) error (failover) handling routines are limited, especially when it comes to how long routines should wait for a change requested by a OS/IIS method call.
To give the user/administrator the ability to control the behavior of xDSCWebService in such conditions there should exist a configuration option which specifies the waiting time for xDSCWebService to wait for operational changes to required objects before an error is reported.
Verbose logs showing the problem
N/A
Suggested solution to the issue
Add a configuration option, that specifies the maximum waiting time specified in milliseconds with a default value of 1000.
[int]WaitingTime = 1000
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
N/A
Version and build of PowerShell the target node is running
N/A
Version of the DSC module that was used ('dev' if using current dev branch)
master/dev
The text was updated successfully, but these errors were encountered:
Details of the scenario you tried and the problem that is occurring
While deploying/retracting a DSC Pullserver the xDSCWebService resource uses IIS and other server objects which might not react instantly when an operation is issued especially when the server is under heavy load or equipped with limited resources like memory or cpu.
Internal (automatic) error (failover) handling routines are limited, especially when it comes to how long routines should wait for a change requested by a OS/IIS method call.
To give the user/administrator the ability to control the behavior of xDSCWebService in such conditions there should exist a configuration option which specifies the waiting time for xDSCWebService to wait for operational changes to required objects before an error is reported.
Verbose logs showing the problem
N/A
Suggested solution to the issue
Add a configuration option, that specifies the maximum waiting time specified in milliseconds with a default value of 1000.
[int]WaitingTime = 1000
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
N/A
Version and build of PowerShell the target node is running
N/A
Version of the DSC module that was used ('dev' if using current dev branch)
master/dev
The text was updated successfully, but these errors were encountered: