-
Oleg Ponomarev authored
In the test provided disk move failover and replace move normally takes place for inst2 in order to avoid all instances running on the same node and satisfy desired locations. * In the first test the avoid-disk-moves *factor* is small and the i optmization performed by a single failover and replace move. * In the second test the avoid-disk-moves *factor* is big enough and failover and replace single move is splitted into two separate steps. That's because gain in cluster score for the failover and replace is not *factor* times bigger than the gain for simple failover move. Signed-off-by: Oleg Ponomarev <onponomarev@gmail.com> Signed-off-by: Klaus Aehlig <aehlig@google.com> Reviewed-by: Klaus Aehlig <aehlig@google.com>
ca084577