Updating on-premises data gateway cluster (with drain)

[ChristiaanB]

Servicing nodes in a typical clustered environment sees the node of interest 'removed from service' (no longer accept new requests), drained (allowed to complete active requests), updated and then reinstated to accept new requests. 

I've been maintaining a load balanced cluster of data gateway machines.  It seems possible to set a particular node to 'disabled' in the cluster using Set-OnPremisesDataGateway PowerShell cmdlet, but the documentation is a little scant on the behaviour (dead stop?), or draining behaviour or not.

I would like to automate and sequence updates, but perform this in a non-disruptive method.  Does anyone know what setting a node to disabled in the cluster (not simply stop the Windows service) results in - instant stop, or to first drain then stop?  Also, how to see if it has drained all active requests before starting maintenance (gateway update, Windows updates, etc)?

I'm thinking along the lines of changing node status in cluster from 'Enabled' to 'Disabled', but node status to show 'Draining' if still completing active request and eventually settle on 'Disabled' once no active requests.  At this point any updates/maintenance can work in safety.  Once maintenance is done set node status in cluster from 'Disabled' to 'Enabled' to resume processing.

Unfortunately I do not have a test environment to experiment in so hoping the community or MS can fill the gap.

[v-luwang-msft]

Hi 

Refer the following article and check if it is helpful.

https://docs.microsoft.com/en-us/data-integration/gateway/service-gateway-high-availability-clusters 

https://docs.microsoft.com/zh-cn/data-integration/gateway/service-gateway-powershell-support

Best Regards

Lucien

[ChristiaanB]

Thanks Lucien.  I have already reviewed those articles and did not find the information I am after.  If I missed the description of how to drain a node please point me in the right direction.  I know how to set a node to disabled, but the elegant removal bit is missing for me.

[krnsrndrn]

How do you disable a node though? As you've said, there is no documentation about these cmdlets and the get-help doesn't offer up any examples. 
I've tried this - 
Set-OnPremisesDataGateway -ClusterObjectId GUID -GatewayObjectId GUID -MemberStatus Disabled

which returned this error - 
Set-OnPremisesDataGateway : Cannot validate argument on parameter 'MemberStatus'. The argument "Disabled" does not belong to the set "None,Enabled" specified by the ValidateSet attribute

So, I tried this - 

Set-OnPremisesDataGateway -ClusterObjectId GUID -GatewayObjectId GUID -MemberStatus None

which returned this error - 

WARNING: The remote server returned an error: (500) Internal Server Error.
WARNING: {"error":{"code":"UnknownError","pbi.error":{"code":"UnknownError"}}}