Fix spotless check

Signed-off-by: Rishab Nahata <rnnahata@amazon.com>
opensearch-project · Dec 20, 2022 · 15615a7 · 15615a7
1 parent 5c67fc3
commit 15615a7
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 3 deletions.
diff --git a/...lusterTest/java/org/opensearch/cluster/coordination/AwarenessAttributeDecommissionIT.java b/...lusterTest/java/org/opensearch/cluster/coordination/AwarenessAttributeDecommissionIT.java
@@ -930,7 +930,8 @@ public void testDecommissionAcknowledgedIfWeightsNotSetForNonRoutingNode() throw
         // Set the timeout to 0 to do immediate Decommission
         DecommissionRequest decommissionRequest = new DecommissionRequest(decommissionAttribute);
         decommissionRequest.setNoDelay(true);
-        DecommissionResponse decommissionResponse = client(dataNodes.get(0)).execute(DecommissionAction.INSTANCE, decommissionRequest).get();
+        DecommissionResponse decommissionResponse = client(dataNodes.get(0)).execute(DecommissionAction.INSTANCE, decommissionRequest)
+            .get();
         assertTrue(decommissionResponse.isAcknowledged());
 
         client(dataNodes.get(0)).admin().cluster().prepareHealth().setWaitForEvents(Priority.LANGUID).get();

diff --git a/server/src/main/java/org/opensearch/cluster/decommission/DecommissionService.java b/server/src/main/java/org/opensearch/cluster/decommission/DecommissionService.java
@@ -416,9 +416,11 @@ private static void validateAwarenessAttribute(
         } else if (forcedAwarenessAttributes.containsKey(decommissionAttribute.attributeName()) == false) {
             msg = "forced awareness attribute [" + forcedAwarenessAttributes.toString() + "] doesn't have the decommissioning attribute";
         }
-        // we don't need to check for attributes presence in forced awareness attribute because, weights API ensures that weights are set for all discovered routing attributes and forced attributes.
+        // we don't need to check for attributes presence in forced awareness attribute because, weights API ensures that weights are set
+        // for all discovered routing attributes and forced attributes.
         // So, if the weight is not present for the attribute it could mean its a non routing node (eg. cluster manager)
-        // And in that case, we are ok to proceed with the decommission. A routing node's attribute absence in forced awareness attribute is a problem elsewhere
+        // And in that case, we are ok to proceed with the decommission. A routing node's attribute absence in forced awareness attribute is
+        // a problem elsewhere
 
         if (msg != null) {
             throw new DecommissioningFailedException(decommissionAttribute, msg);