You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace internal usages of 'master' term in 'server/src/main' directory (#2519)
* Replace internal usages of 'master' terminology in server/src/main directory
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Restore rename DISCOVERED_MASTER in ClusterHealthResponse
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Rename two methods in unit tests
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Replace master word in ClusterState
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Replace master word in LeaderChecker JoinHelper JoinTaskExecutor
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Replace master word in more classes
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Replace master word in more classes
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Replace master word in more classes
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Replace master word in more classes
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Replace master word in more classes
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Replace master word in more classes
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Replace master word in DiscoveryNodes classes
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Replace master word in more classes
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Correct mistakes
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Adjust format by spotlessApply task
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Change MASTER__NODE_BOOTSTRAPPED_MSG in test
Signed-off-by: Tianli Feng <ftianli@amazon.com>
* Fix SnapshotDisruptionIT by renaming to cluster-manager
Signed-off-by: Tianli Feng <ftianli@amazon.com>
Copy file name to clipboardexpand all lines: server/src/internalClusterTest/java/org/opensearch/cluster/coordination/UnsafeBootstrapAndDetachCommandIT.java
Copy file name to clipboardexpand all lines: server/src/main/java/org/opensearch/action/admin/cluster/allocation/TransportClusterAllocationExplainAction.java
+1-1
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@
64
64
65
65
/**
66
66
* The {@code TransportClusterAllocationExplainAction} is responsible for actually executing the explanation of a shard's allocation on the
Copy file name to clipboardexpand all lines: server/src/main/java/org/opensearch/action/admin/cluster/repositories/cleanup/TransportCleanupRepositoryAction.java
+4-4
Original file line number
Diff line number
Diff line change
@@ -73,12 +73,12 @@
73
73
* <ol>
74
74
* <li>Check that there are no running repository cleanup, snapshot create, or snapshot delete actions
75
75
* and add an entry for the repository that is to be cleaned up to {@link RepositoryCleanupInProgress}</li>
76
-
* <li>Run cleanup actions on the repository. Note, these are executed exclusively on the master node.
76
+
* <li>Run cleanup actions on the repository. Note, these are executed exclusively on the cluster-manager node.
77
77
* For the precise operations execute see {@link BlobStoreRepository#cleanup}</li>
78
78
* <li>Remove the entry in {@link RepositoryCleanupInProgress} in the first step.</li>
79
79
* </ol>
80
80
*
81
-
* On master failover during the cleanup operation it is simply removed from the cluster state. This is safe because the logic in
81
+
* On cluster-manager failover during the cleanup operation it is simply removed from the cluster state. This is safe because the logic in
82
82
* {@link BlobStoreRepository#cleanup} ensures that the repository state id has not changed between creation of the cluster state entry
83
83
* and any delete/write operations. TODO: This will not work if we also want to clean up at the shard level as those will involve writes
84
84
* as well as deletes.
@@ -119,7 +119,7 @@ public TransportCleanupRepositoryAction(
119
119
);
120
120
this.repositoriesService = repositoriesService;
121
121
this.snapshotsService = snapshotsService;
122
-
// We add a state applier that will remove any dangling repository cleanup actions on master failover.
122
+
// We add a state applier that will remove any dangling repository cleanup actions on cluster-manager failover.
123
123
// This is safe to do since cleanups will increment the repository state id before executing any operations to prevent concurrent
124
124
// operations from corrupting the repository. This is the same safety mechanism used by snapshot deletes.
125
125
if (DiscoveryNode.isMasterNode(clusterService.getSettings())) {
Copy file name to clipboardexpand all lines: server/src/main/java/org/opensearch/action/admin/cluster/settings/TransportClusterUpdateSettingsAction.java
+4-4
Original file line number
Diff line number
Diff line change
@@ -155,11 +155,11 @@ public void onAckTimeout() {
Copy file name to clipboardexpand all lines: server/src/main/java/org/opensearch/action/admin/cluster/snapshots/restore/RestoreClusterStateListener.java
+2-2
Original file line number
Diff line number
Diff line change
@@ -69,8 +69,8 @@ public void clusterChanged(ClusterChangedEvent changedEvent) {
Copy file name to clipboardexpand all lines: server/src/main/java/org/opensearch/action/admin/cluster/snapshots/status/TransportSnapshotsStatusAction.java
+3-3
Original file line number
Diff line number
Diff line change
@@ -221,8 +221,8 @@ private void buildResponse(
221
221
// Unlikely edge case:
222
222
// Data node has finished snapshotting the shard but the cluster state has not yet been updated
223
223
// to reflect this. We adjust the status to show up as snapshot metadata being written because
224
-
// technically if the data node failed before successfully reporting DONE state to master, then
225
-
// this shards state would jump to a failed state.
224
+
// technically if the data node failed before successfully reporting DONE state to cluster-manager,
225
+
// then this shards state would jump to a failed state.
226
226
shardStatus = newSnapshotIndexShardStatus(
227
227
shardEntry.key,
228
228
SnapshotIndexShardStage.FINALIZE,
@@ -406,7 +406,7 @@ private SnapshotInfo snapshot(SnapshotsInProgress snapshotsInProgress, String re
406
406
/**
407
407
* Returns status of shards currently finished snapshots
408
408
* <p>
409
-
* This method is executed on master node and it's complimentary to the
409
+
* This method is executed on cluster-manager node and it's complimentary to the
410
410
* {@link SnapshotShardsService#currentSnapshotShards(Snapshot)} because it
411
411
* returns similar information but for already finished snapshots.
0 commit comments