Issue upgrade from 6.7 to 7 for single node


(fayaz) #1

Hi

I am trying to upgrade from 6.7 to 7 for elasticsearch. I am running my elastic search on single server with one node cluster. I see several warnings. How can I fix this.

Here is my configuration.

network.host: 0.0.0.0
# --------------------------------- Discovery ----------------------------------
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
discovery.seed_hosts: ["prod.server.com"]
# Bootstrap the cluster using an initial set of master-eligible nodes:
cluster.initial_master_nodes: node-1

Error log

[2019-04-13T19:27:52,711][WARN ][o.e.c.c.ClusterFormationFailureHelper] [prod.server.com] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [node-1] to bootstrap a cluster: have discovered []; discovery will continue using [127.0.0.1:9300, 127.0.0.1:9301, 127.0.0.1:9302, 127.0.0.1:9303, 127.0.0.1:9304, [::1]:9300, [::1]:9301, [::1]:9302, [::1]:9303, [::1]:9304] from hosts providers and [{prod.server.com}{jG4MSlobSo2gNfA8Qdlzfw}{9KdamOMLQNKD2LpJCmm84w}{10.44.10.140}{10.44.10.140:9300}{ml.machine_memory=7674531840, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
[2019-04-13T19:28:14,617][WARN ][r.suppressed             ] [prod.server.com] path: /.kibana/doc/kql-telemetry%3Akql-telemetry, params: {index=.kibana, id=kql-telemetry:kql-telemetry, type=doc}
org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];
        at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedException(ClusterBlocks.java:191) ~[elasticsearch-7.0.0.jar:7.0.0]
        at org.elasticsearch.action.support.single.shard.TransportSingleShardAction.checkGlobalBlock(TransportSingleShardAction.java:126) ~[elasticsearch-7.0.0.jar:7.0.0]
        at org.elasticsearch.action.support.single.shard.TransportSingleShardAction$AsyncSingleAction.<init>(TransportSingleShardAction.java:160) ~[elasticsearch-7.0.0.jar:7.0.0]

Filebeat for Raspberry Pi
(David Pilato) #2

Where this setting is coming from prod.server.com?


(fayaz) #3

@dadoonet sorry< i just removed it for security reasons. Its the same thing you are seeing now in config file.


(David Pilato) #4

What is this?

cluster.initial_master_nodes: node-1

(fayaz) #5

When I upgraded my Elastic search Inititally I got error starting ES. Added the from this reply.


(David Pilato) #6

Sure but node-1 does not exist in your configuration. It's not your node name. It should be I guess prod.server.com?


(fayaz) #7

Sure, Let me try. Thank you.


(fayaz) #8

@dadoonet

I made that change and the elastic search starts good but I see this in logs. Is it because I'm still using kibana 6.7?

[2019-04-14T09:21:40,379][WARN ][r.suppressed             ] [reldev0000318.ags.esri.com] path: /.kibana_task_manager/_doc/_search, params: {ignore_unavailable=true, index=.kibana_task_manager, type=_doc}
org.elasticsearch.action.search.SearchPhaseExecutionException: all shards failed
        at org.elasticsearch.action.search.AbstractSearchAsyncAction.onPhaseFailure(AbstractSearchAsyncAction.java:296) ~[elasticsearch-7.0.0.jar:7.0.0]
        at org.elasticsearch.action.search.AbstractSearchAsyncAction.executeNextPhase(AbstractSearchAsyncAction.java:139) ~[elasticsearch-7.0.0.jar:7.0.0]
        at org.elasticsearch.action.search.AbstractSearchAsyncAction.onPhaseDone(AbstractSearchAsyncAction.java:259) ~[elasticsearch-7.0.0.jar:7.0.0]

(David Pilato) #9

You must use the same version.