From 7e9a186fa2f9197637071b87e7e5e6ada8f33b14 Mon Sep 17 00:00:00 2001 From: Onur Tirtir Date: Fri, 6 Oct 2023 12:10:46 +0300 Subject: [PATCH] comment --- .../operations/rebalancer_placement_isolation.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/backend/distributed/operations/rebalancer_placement_isolation.c b/src/backend/distributed/operations/rebalancer_placement_isolation.c index 415e2f074..9af57dd3d 100644 --- a/src/backend/distributed/operations/rebalancer_placement_isolation.c +++ b/src/backend/distributed/operations/rebalancer_placement_isolation.c @@ -177,10 +177,11 @@ NodeToPlacementGroupHashInit(HTAB *nodePlacementGroupHash, List *activeWorkerNod * * For this reason, below we find out the assigned placement groups for * nodes of type S because we want to avoid from moving the placements - * (if any) from a node of type D to S. We also set - * allowedToSeparateAnyPlacementGroup to false for the nodes that already - * have some shard placements within S because we want to avoid from moving - * the placements that need a separate node (if any) from node D to node S. + * (if any) from a node of type D to a node that is used to separate a + * placement group within S. We also set allowedToSeparateAnyPlacementGroup + * to false for the nodes that already have some shard placements within S + * because we want to avoid from moving the placements that need a separate + * node (if any) from node D to node S. * * We skip below code for nodes of type D not because optimization purposes * but because it would be "incorrect" to assume that "current placement