Open crazymind1337 opened 1 year ago
"number_of_data_nodes" : 1,
"active_primary_shards" : 4,
"active_shards" : 4,
"unassigned_shards" : 3,
From the docs:
A yellow cluster status means the primary shards for all indexes are allocated to nodes in a cluster, but the replica shards for at least one index aren't.
You only have one node, but the replica shard needs to be on a different node.
I have replicated this behavior with the RPM package (fresh install), this does not happen in 2.8.0
, I also get the same log errors/warnings
Apparently, the unassigned shards are duplicated:
.plugins-ml-config 0 r UNASSIGNED
.opensearch-sap-pre-packaged-rules-config 0 r UNASSIGNED
.opensearch-sap-log-types-config 0 r UNASSIGNED
Note: This appears to be solved in 2.10.0
[root@centos7 vagrant]# curl -k -u admin:admin https://localhost:9200/_cat/shards
.opensearch-observability 0 p STARTED 0 208b 127.0.0.1 centos7
.opensearch-sap-log-types-config 0 p STARTED 127.0.0.1 centos7
.opendistro_security 0 p STARTED 10 75.4kb 127.0.0.1 centos7
indeed, the problem is solved on opensearch 2.10 and 2.11
The warning "Failed to initialize LogType config index and builtin log types" as mentioned in the issue title is still present in version 2.11 It seems that the creation of the index is always triggered and produces the warning, if index already exists. The cluster status is green though.
Describe the bug I am trying to install the new version of opensearch on Ubuntu 20.04. But the cluster state stays at yellow.
To Reproduce Steps to reproduce the behavior:
Expected behavior Cluster state becomes green.
Plugins Basic installation.
Screenshots %
Host/Environment (please complete the following information):
Additional context In the logs of opensearch I am able to discover the following informations:
Complete log can be found at: https://justpaste.it/c9c32