Strange Rebalancing Problem

[Manfred Blum]

Hello,

we have a strange problem since updating PVS Server from 1912 LTSR CU4 to 2203LTSR CU1.

We have two PVS Server and several Server-Targets on Citrix Hypervisor. Normally we assign a specific target device type (vhd) to a specific PVS Server (using the Load-Balancing entry of the vdisk).
To move the targets to the other PVS Server (for maintenance purpose), we simply change the Load-Balancing Server and do a rebalance of the current server.
This worked without problems with 1912. Now it does not work anymore.
If I change the Load-Balancing to "Use the load balancing algorithm" with eg Best Effort, the Targets change to the other server until both servers hold the same count of targets.
If I change all targets to "Use the load balancing algorithm" and stop the Streaming Service on one PVS Server, all Targets move to the other server.
It simply seems, that the Rebalance does not work anymore with Load-Balancing set to a specific Server.

Is this perhaps a Bug? Does anyone have the same problem? A solution?

 

Kind Regards

Manfred
 

[Carl Fallis]

With Provisioning 2203 CU2 we have added a reconnect option to the console that will allow you to select targets to reconnect.  This tells the targets to start the reconnect process, it does not guarantee that the target will connect to a different server.  When a target reconnects the login server it connects to determines what Provisioning server the target should connect to for IO not the target. 

[Kelan Rowe]

With the Provisioning Services 2203 release (and above), the manual rebalance logic is changed to load-based rebalance, wherein only the over-loaded targets connected to the server are forced to reconnect. Reblanace devices is also only effective on vdisks which are in a HA configuration (so excludes vdisks which are provided by a single PVS server). 

[Manfred Blum]

On 12/15/2022 at 2:46 PM, Carl Fallis said:

With Provisioning 2203 CU2 we have added a reconnect option to the console that will allow you to select targets to reconnect.  This tells the targets to start the reconnect process, it does not guarantee that the target will connect to a different server.  When a target reconnects the login server it connects to determines what Provisioning server the target should connect to for IO not the target. 

Hello Carl,
thank you, works like a charm!