OpenSearch single node not initializing : Stuck at waiting for yellow cluster state

Versions (relevant - OpenSearch/Dashboard/Server OS/Browser):
OpenSearch v2.5 single node running on Linux (oracle 8.5)
Describe the issue:
I am trying to get a single master node up using the default security settings and default certs but it appears that the node is not getting initialized. I am planning to add more nodes to the cluster after I manage to the get the single master node initialized. Any ideas on what Im doing wrong?

Configuration:
plugins.security.ssl.transport.pemcert_filepath: esnode.pem
plugins.security.ssl.transport.pemkey_filepath: esnode-key.pem
plugins.security.ssl.transport.pemtrustedcas_filepath: root-ca.pem
plugins.security.ssl.transport.enforce_hostname_verification: false
plugins.security.ssl.http.enabled: true
plugins.security.ssl.http.pemcert_filepath: esnode.pem
plugins.security.ssl.http.pemkey_filepath: esnode-key.pem
plugins.security.ssl.http.pemtrustedcas_filepath: root-ca.pem
plugins.security.allow_unsafe_democertificates: true
plugins.security.allow_default_init_securityindex: true
plugins.security.authcz.admin_dn:

  • CN=kirk,OU=client,O=client,L=test, C=de

plugins.security.audit.type: internal_opensearch
plugins.security.enable_snapshot_restore_privilege: true
plugins.security.check_snapshot_restore_write_privileges: true
plugins.security.restapi.roles_enabled: [“all_access”, “security_rest_api_access”]
plugins.security.system_indices.enabled: true
plugins.security.system_indices.indices: [“.plugins-ml-model”, “.plugins-ml-task”, “.opendistro-alerting-config”, “.opendistro-alerting-alert*”, “.opendistro-anomaly-results*”, “.opendistro-anomaly-detector*”, “.opendistro-anomaly-checkpoints”, “.opendistro-anomaly-detection-state”, “.opendistro-reports-", ".opensearch-notifications-”, “.opensearch-notebooks”, “.opensearch-observability”, “.opendistro-asynchronous-search-response*”, “.replication-metadata-store”]
node.max_local_storage_nodes: 3
cluster.name: opensearch-cluster
node.name: opensearch-cluster_manager
node.roles: [ cluster_manager ]
#network.host: 10.223.16.16
plugins.security.disabled: false
discovery.seed_hosts: [localhost]
#cluster.initial_master_nodes: opensearch-cluster_manager
strong text

Relevant Logs or Screenshots:
Security Admin v7
Will connect to localhost:9200 … done
Connected as “CN=kirk,OU=client,O=client,L=test,C=de”
OpenSearch Version: 2.5.0
Contacting opensearch cluster ‘opensearch’ and wait for YELLOW clusterstate …

Relevant Logs or Screenshots:

[2023-03-19T10:25:29,329][INFO ][o.o.n.Node ] [opensearch-cluster_manager] initialized
[2023-03-19T10:25:29,330][INFO ][o.o.n.Node ] [opensearch-cluster_manager] starting …
[2023-03-19T10:25:29,572][INFO ][o.o.t.TransportService ] [opensearch-cluster_manager] publish_address {127.0.0.1:9300}, bound_addresses {[::1]:9300}, {127.0.0.1:9300}
[2023-03-19T10:25:29,960][INFO ][o.o.c.c.Coordinator ] [opensearch-cluster_manager] cluster UUID [L2_Dol1KQi-PoLt9HsMuZg]
[2023-03-19T10:25:30,121][INFO ][o.o.c.s.MasterService ] [opensearch-cluster_manager] elected-as-cluster-manager ([1] nodes joined)[{opensearch-cluster_manager}{ejPsOWRtQ3K3wElJOzLgvA}{cA2ZPBekRga5Ze525R13QA}{127.0.0.1}{127.0.0.1:9300}{m}{shard_indexing_pressure_enabled=true} elect leader, BECOME_CLUSTER_MANAGER_TASK, FINISH_ELECTION], term: 7, version: 26, delta: cluster-manager node changed {previous , current [{opensearch-cluster_manager}{ejPsOWRtQ3K3wElJOzLgvA}{cA2ZPBekRga5Ze525R13QA}{127.0.0.1}{127.0.0.1:9300}{m}{shard_indexing_pressure_enabled=true}]}
[2023-03-19T10:25:30,190][INFO ][o.o.c.s.ClusterApplierService] [opensearch-cluster_manager] cluster-manager node changed {previous , current [{opensearch-cluster_manager}{ejPsOWRtQ3K3wElJOzLgvA}{cA2ZPBekRga5Ze525R13QA}{127.0.0.1}{127.0.0.1:9300}{m}{shard_indexing_pressure_enabled=true}]}, term: 7, version: 26, reason: Publication{term=7, version=26}
[2023-03-19T10:25:30,201][INFO ][o.o.a.c.ADClusterEventListener] [opensearch-cluster_manager] Cluster is not recovered yet.
[2023-03-19T10:25:30,208][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [opensearch-cluster_manager] Detected cluster change event for destination migration
[2023-03-19T10:25:30,235][INFO ][o.o.i.i.ManagedIndexCoordinator] [opensearch-cluster_manager] Cache cluster manager node onClusterManager time: 1679201730235
[2023-03-19T10:25:30,248][WARN ][o.o.p.c.s.h.ConfigOverridesClusterSettingHandler] [opensearch-cluster_manager] Config override setting update called with empty string. Ignoring.
[2023-03-19T10:25:30,256][INFO ][o.o.d.PeerFinder ] [opensearch-cluster_manager] setting findPeersInterval to [1s] as node commission status = [true] for local node [{opensearch-cluster_manager}{ejPsOWRtQ3K3wElJOzLgvA}{cA2ZPBekRga5Ze525R13QA}{127.0.0.1}{127.0.0.1:9300}{m}{shard_indexing_pressure_enabled=true}]
[2023-03-19T10:25:30,268][INFO ][o.o.h.AbstractHttpServerTransport] [opensearch-cluster_manager] publish_address {127.0.0.1:9200}, bound_addresses {[::1]:9200}, {127.0.0.1:9200}
[2023-03-19T10:25:30,269][INFO ][o.o.n.Node ] [opensearch-cluster_manager] started
[2023-03-19T10:25:30,269][INFO ][o.o.s.OpenSearchSecurityPlugin] [opensearch-cluster_manager] Node started
[2023-03-19T10:25:30,270][INFO ][o.o.s.c.ConfigurationRepository] [opensearch-cluster_manager] Will attempt to create index .opendistro_security and default configs if they are absent
[2023-03-19T10:25:30,273][INFO ][o.o.s.OpenSearchSecurityPlugin] [opensearch-cluster_manager] 0 OpenSearch Security modules loaded so far:
[2023-03-19T10:25:30,275][INFO ][o.o.s.c.ConfigurationRepository] [opensearch-cluster_manager] Background init thread started. Install default config?: true
[2023-03-19T10:25:30,308][INFO ][o.o.c.s.ClusterSettings ] [opensearch-cluster_manager] updating [plugins.index_state_management.template_migration.control] from [0] to [-1]
[2023-03-19T10:25:30,312][INFO ][o.o.a.c.HashRing ] [opensearch-cluster_manager] Node added: [ejPsOWRtQ3K3wElJOzLgvA]
[2023-03-19T10:25:30,314][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [opensearch-cluster_manager] Detected cluster change event for destination migration
[2023-03-19T10:25:30,318][INFO ][o.o.a.c.HashRing ] [opensearch-cluster_manager] All nodes with known AD version: {ejPsOWRtQ3K3wElJOzLgvA=ADNodeInfo{version=2.5.0, isEligibleDataNode=false}}
[2023-03-19T10:25:30,319][INFO ][o.o.a.c.HashRing ] [opensearch-cluster_manager] Rebuild AD hash ring for realtime AD with cooldown, nodeChangeEvents size 0
[2023-03-19T10:25:30,319][INFO ][o.o.a.c.HashRing ] [opensearch-cluster_manager] Build AD version hash ring successfully
[2023-03-19T10:25:30,320][INFO ][o.o.a.c.ADClusterEventListener] [opensearch-cluster_manager] Init AD version hash ring successfully
[2023-03-19T10:25:30,359][INFO ][o.o.g.GatewayService ] [opensearch-cluster_manager] recovered [1] indices into cluster_state
[2023-03-19T10:25:30,371][INFO ][o.o.s.c.ConfigurationRepository] [opensearch-cluster_manager] Index .opendistro_security already exists
[2023-03-19T10:25:30,371][INFO ][o.o.s.c.ConfigurationRepository] [opensearch-cluster_manager] Node started, try to initialize it. Wait for at least yellow cluster state…
[2023-03-19T10:26:30,238][INFO ][o.o.i.i.ManagedIndexCoordinator] [opensearch-cluster_manager] Performing move cluster state metadata.
[2023-03-19T10:26:30,239][INFO ][o.o.i.i.MetadataService ] [opensearch-cluster_manager] ISM config index not exist, so we cancel the metadata migration job.
[2023-03-19T10:27:30,238][INFO ][o.o.i.i.ManagedIndexCoordinator] [opensearch-cluster_manager] Cancel background move metadata process.
[2023-03-19T10:27:30,239][INFO ][o.o.i.i.ManagedIndexCoordinator] [opensearch-cluster_manager] Performing move cluster state metadata.
[2023-03-19T10:27:30,240][INFO ][o.o.i.i.MetadataService ] [opensearch-cluster_manager] Move metadata has finished.
[2023-03-19T10:30:29,965][INFO ][o.o.j.s.JobSweeper ] [opensearch-cluster_manager] Running full sweep
[2023-03-19T10:30:30,243][INFO ][o.o.i.i.PluginVersionSweepCoordinator] [opensearch-cluster_manager] Canceling sweep ism plugin version job
[2023-03-19T10:35:29,968][INFO ][o.o.j.s.JobSweeper ] [opensearch-cluster_manager] Running full sweep
[2023-03-19T10:36:06,529][ERROR][o.o.s.a.BackendRegistry ] [opensearch-cluster_manager] Not yet initialized (you may need to run securityadmin)

Its asking me to run the SecurityAdmin but when I run SecurityAdmin it says waiting for Node to be yellow.

Try to run security admin with the “-arc” parameter.
But if the cluster is yellow then there is probably something with replica settings that is keeping it yellow (ie shards not initialized yet)

My Issue is that the cluster is stuck in RED state and not moving to yellow, From the opensearch side it says I need to run to SecurityAdmin and when I do run SecurityAdmin it says that the cluster is in RED and it fails when using the -arc parameter. It seems like Im unable to move forward and stuck from both sides…

@Amith Have you found a solution to your issue?

I was able to initialize the node after clearing the folders and files in /opensearch-2.6.0/data/ folder. I was just setting this up initially and there was no real data/indexes present.

Regards,
Amith

1 Like