Deprecate the Master nomenclature in 2.0 (opensearch-project#415)

Signed-off-by: Subhobrata Dey <[email protected]> Signed-off-by: Angie Zhang <[email protected]>
Angie-Zhang · Jun 29, 2022 · 96f868e · 96f868e
1 parent 76b3107
commit 96f868e
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/alerting/src/main/kotlin/org/opensearch/alerting/alerts/AlertIndices.kt b/alerting/src/main/kotlin/org/opensearch/alerting/alerts/AlertIndices.kt
@@ -56,7 +56,7 @@ import java.time.Instant
  * date based index. The frequency of rolling over indices is controlled by the `opendistro.alerting.alert_rollover_period` setting.
  *
  * These indexes are created when first used and are then rolled over every `alert_rollover_period`. The rollover is
- * initiated on the master node to ensure only a single node tries to roll it over.  Once we have a curator functionality
+ * initiated on the cluster manager node to ensure only a single node tries to roll it over.  Once we have a curator functionality
  * in Scheduled Jobs we can migrate to using that to rollover the index.
  */
 // TODO: reafactor to make a generic version of this class for finding and alerts

diff --git a/core/src/main/kotlin/org/opensearch/alerting/core/JobSweeper.kt b/core/src/main/kotlin/org/opensearch/alerting/core/JobSweeper.kt
@@ -138,7 +138,7 @@ class JobSweeper(
      * the cluster, a replica is added, removed or promoted to primary).
      *
      * This callback won't be invoked concurrently since cluster state changes are applied serially to the node
-     * in the order they occur on the master. However we can't block this callback for the duration of a full sweep so
+     * in the order they occur on the cluster manager. However we can't block this callback for the duration of a full sweep so
      * we perform the sweep in the background in a single threaded executor [fullSweepExecutor].
      */
     override fun clusterChanged(event: ClusterChangedEvent) {