Kibana, Evaraina use chestunnara?

[jefferson1]

3 minutes ago, ahimsavaadhi1 said:

Two hosts for elastic search , they will always have yellow. Either go with single node or go with 3. 
 

also why windows ? Use kubernetes or docker cluster.

ma software ki dependency undi, it is deployed on windows and uses ES. 

yesterday it  showed green  and now changed to yellow

this is tthte config i  am uusing, tell me where i am doing wrong

 

 

action.auto_create_index: .monitoring*,.watches,.triggered_watches,.watcher-history*,.ml
cluster.name: elasticsearch
node.name: abcd
path.data: E:\genesys\apps\GCTI\elasticsearch-8.10.2\data
path.logs: E:\genesys\apps\GCTI\elasticsearch-8.10.2\logs
bootstrap.memory_lock: true
network.host: abcd
http.port: 9200
discovery.seed_hosts: ["abcd","abce"]
cluster.initial_master_nodes: ["abcd"]
xpack.security.enabled: false
xpack.security.enrollment.enabled: false
xpack.security.http.ssl:
  enabled: false
  keystore.path: certs/http.p12
xpack.security.transport.ssl:
  enabled: false
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12

[ahimsavaadhi1]

11 minutes ago, jefferson1 said:

ma software ki dependency undi, it is deployed on windows and uses ES. 

yesterday it  showed green  and now changed to yellow

this is tthte config i  am uusing, tell me where i am doing wrong

 

 

action.auto_create_index: .monitoring*,.watches,.triggered_watches,.watcher-history*,.ml
cluster.name: elasticsearch
node.name: abcd
path.data: E:\genesys\apps\GCTI\elasticsearch-8.10.2\data
path.logs: E:\genesys\apps\GCTI\elasticsearch-8.10.2\logs
bootstrap.memory_lock: true
network.host: abcd
http.port: 9200
discovery.seed_hosts: ["abcd","abce"]
cluster.initial_master_nodes: ["abcd"]
xpack.security.enabled: false
xpack.security.enrollment.enabled: false
xpack.security.http.ssl:
  enabled: false
  keystore.path: certs/http.p12
xpack.security.transport.ssl:
  enabled: false
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12

ES logs lo there might be a warning message . Can you copy the content ? 

[ahimsavaadhi1]

12 minutes ago, jefferson1 said:

ma software ki dependency undi, it is deployed on windows and uses ES. 

yesterday it  showed green  and now changed to yellow

this is tthte config i  am uusing, tell me where i am doing wrong

 

 

action.auto_create_index: .monitoring*,.watches,.triggered_watches,.watcher-history*,.ml
cluster.name: elasticsearch
node.name: abcd
path.data: E:\genesys\apps\GCTI\elasticsearch-8.10.2\data
path.logs: E:\genesys\apps\GCTI\elasticsearch-8.10.2\logs
bootstrap.memory_lock: true
network.host: abcd
http.port: 9200
discovery.seed_hosts: ["abcd","abce"]
cluster.initial_master_nodes: ["abcd"]
xpack.security.enabled: false
xpack.security.enrollment.enabled: false
xpack.security.http.ssl:
  enabled: false
  keystore.path: certs/http.p12
xpack.security.transport.ssl:
  enabled: false
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12

Bro, also curious why this CTi, go with aws connect or twilio no.

much better experience and nothing to manage. 

[jefferson1]

2 minutes ago, ahimsavaadhi1 said:

ES logs lo there might be a warning message . Can you copy the content ? 

[2023-09-28T15:44:55,789][WARN ][o.e.c.c.Coordinator      ] [abcd] This node is a fully-formed single-node cluster with cluster UUID [RyQkGwRKTdybisChMoSRQ], but it is configured as if to discover other nodes and form a multi-node cluster via the [discovery.seed_hosts=[abcd, abce]] setting. Fully-formed clusters do not attempt to discover other nodes, and nodes with different cluster UUIDs cannot belong to the same cluster. The cluster UUID persists across restarts and can only be changed by deleting the contents of the node's data path(s). Remove the discovery configuration to suppress this message.

[ahimsavaadhi1]

2 minutes ago, jefferson1 said:

[2023-09-28T15:44:55,789][WARN ][o.e.c.c.Coordinator      ] [abcd] This node is a fully-formed single-node cluster with cluster UUID [RyQkGwRKTdybisChMoSRQ], but it is configured as if to discover other nodes and form a multi-node cluster via the [discovery.seed_hosts=[abcd, abce]] setting. Fully-formed clusters do not attempt to discover other nodes, and nodes with different cluster UUIDs cannot belong to the same cluster. The cluster UUID persists across restarts and can only be changed by deleting the contents of the node's data path(s). Remove the discovery configuration to suppress this message.

Ee line comment chesi elastic service ni restart cheyyi.

#discovery.seed_hosts: ["abcd","abce"]

[jefferson1]

2 minutes ago, ahimsavaadhi1 said:

Ee line comment chesi elastic service ni restart cheyyi.

#discovery.seed_hosts: ["abcd","abce"]

by doing so, does one  host know about other host

[jefferson1]

4 minutes ago, ahimsavaadhi1 said:

Ee line comment chesi elastic service ni restart cheyyi.

#discovery.seed_hosts: ["abcd","abce"]

same as before

 

[2023-09-28T15:52:47,097][INFO ][o.e.c.r.a.AllocationService] [abcd] current.health="YELLOW" message="Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[default_sm_index_english][4]]])." previous.health="RED" reason="shards started [[default_sm_index_english][4]]"

[ahimsavaadhi1]

1 minute ago, jefferson1 said:

by doing so, does one  host know about other host

 [abcd] This node is a fully-formed single-node cluster with cluster UUID[RyQkGwRKTdybisChMoSRQ], 

not sure how it is architected. But the above log is saying this node “abcd” is fully formed cluster (single node es ) and it should not look at discovering other nodes. 
 

Kibana lo screen shot post chesthava ? 

[ahimsavaadhi1]

3 minutes ago, jefferson1 said:

same as before

 

[2023-09-28T15:52:47,097][INFO ][o.e.c.r.a.AllocationService] [abcd] current.health="YELLOW" message="Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[default_sm_index_english][4]]])." previous.health="RED" reason="shards started [[default_sm_index_english][4]]"

https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html

[jefferson1]

3 minutes ago, ahimsavaadhi1 said:

 [abcd] This node is a fully-formed single-node cluster with cluster UUID[RyQkGwRKTdybisChMoSRQ], 

not sure how it is architected. But the above log is saying this node “abcd” is fully formed cluster (single node es ) and it should not look at discovering other nodes. 
 

Kibana lo screen shot post chesthava ? 

didn't install kibana. windows sever meeda installl cheyala or local PC

[ahimsavaadhi1]

3 minutes ago, jefferson1 said:

didn't install kibana. windows sever meeda installl cheyala or local PC

Oh ok. There is no kibana ?  So it’s just elastic stack for logging and querying.

then how were  you suggesting it’s yellow , I know you have logs. 

[ahimsavaadhi1]

1 hour ago, jefferson1 said:

same as before

 

[2023-09-28T15:52:47,097][INFO ][o.e.c.r.a.AllocationService] [abcd] current.health="YELLOW" message="Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[default_sm_index_english][4]]])." previous.health="RED" reason="shards started [[default_sm_index_english][4]]"

Also there has to some more events before or after this. 
 

it probably would say replication shards not there …. Or something to that affect 

[TKWQ]

Copy paste from google:

Elasticsearch will never assign a replica to the same node as the primary shard, so if you only have one node it is perfectly normal and expected for your cluster to indicate yellow. If you feel better about it being green, then change the number of replicas on each index to be 0.

 

Also, Kibana is not to administrate ES.