Upgrade from ELK 7.7.1 to ELK 8.4.1

Elastic Stack Elasticsearch
1

I upgraded recently ELK 7.7.1 to ELK 8.4.1.
I am looking out the logs of ELK 8.4.1, finds the below logs. Is there any view point from these logs.

{"@timestamp":"2022-09-15T16:17:36.167Z", "log.level": "WARN", "message":"[[.monitoring-es-7-2022.09.15][0]] failed to perform indices:data/write/bulk[s] on replica [.monitoring-es-7-2022.09.15][0], node[iyjlLKIZTxmbnjGfPiwklw], [R], s[STARTED], a[id=Iwx3Qw3iSLGraYWqHn2eCg]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[quickstart-es-hot-data-nodes-2][scheduler][T#1]","log.logger":"org.elasticsearch.action.bulk.TransportShardBulkAction","elasticsearch.cluster.uuid":"iPNttxpSQ1OrM_htODRLAw","elasticsearch.node.id":"Ih4tdykdQlO-5X9EGcLG_Q","elasticsearch.node.name":"quickstart-es-hot-data-nodes-2","elasticsearch.cluster.name":"quickstart","error.type":"org.elasticsearch.client.internal.transport.NoNodeAvailableException","error.message":"unknown node [iyjlLKIZTxmbnjGfPiwklw]","error.stack_trace":"org.elasticsearch.client.internal.transport.NoNodeAvailableException: unknown node [iyjlLKIZTxmbnjGfPiwklw]\n\tat org.elasticsearch.server@8.4.1/org.elasticsearch.action.support.replication.TransportReplicationAction$ReplicasProxy.performOn(TransportReplicationAction.java:1264)\n\tat org.elasticsearch.server@8.4.1/org.elasticsearch.action.support.replication.ReplicationOperation$3.tryAction(ReplicationOperation.java:280)\n\tat org.elasticsearch.server@8.4.1/org.elasticsearch.action.support.RetryableAction$1.doRun(RetryableAction.java:100)\n\tat org.elasticsearch.server@8.4.1/org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:769)\n\tat org.elasticsearch.server@8.4.1/org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26)\n\tat org.elasticsearch.server@8.4.1/org.elasticsearch.threadpool.ThreadPool$1.run(ThreadPool.java:436)\n\tat java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)\n\tat java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)\n\tat java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)\n\tat java.base/java.lang.Thread.run(Thread.java:833)\n\tSuppressed: org.elasticsearch.transport.NodeNotConnectedException: [quickstart-es-hot-data-nodes-0][10.192.10.106:9300] Node not connected\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.transport.ClusterConnectionManager.getConnection(ClusterConnectionManager.java:280)\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.transport.TransportService.getConnection(TransportService.java:808)\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.transport.TransportService.sendRequest(TransportService.java:718)\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.action.support.replication.TransportReplicationAction$ReplicasProxy.performOn(TransportReplicationAction.java:1278)\n\t\t... 11 more\n\tSuppressed: org.elasticsearch.transport.NodeNotConnectedException: [quickstart-es-hot-data-nodes-0][10.192.10.106:9300] Node not connected\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.transport.ClusterConnectionManager.getConnection(ClusterConnectionManager.java:280)\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.transport.TransportService.getConnection(TransportService.java:808)\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.transport.TransportService.sendRequest(TransportService.java:718)\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.action.support.replication.TransportReplicationAction$ReplicasProxy.performOn(TransportReplicationAction.java:1278)\n\t\t... 11 more\n\tSuppressed: org.elasticsearch.transport.NodeNotConnectedException: [quickstart-es-hot-data-nodes-0][10.192.10.106:9300] Node not connected\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.transport.ClusterConnectionManager.getConnection(ClusterConnectionManager.java:280)\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.transport.TransportService.getConnection(TransportService.java:808)\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.transport.TransportService.sendRequest(TransportService.java:718)\n\t\tat org.elasticsearch.server@8.4.1/org.elasticsearch.action.support.replication.TransportReplicationAction$ReplicasProxy.performOn(TransportReplicationAction.java:1278)\n\t\t... 11 more\n"}

2

Did you follow the steps outlined in the documentation and first go to version 7.17 and run the upgrade assistant?

1 Like
3

I did not follow these steps...as this ELK containers... we downloaded 8.4.1 ELK image and uploaded image to our local repo... applied the same repo to upgrade.

4

The upgrade still applies even if you are running on containers. I have not had these issues so the log entries doesn't tell me anything. I would recommend sharing more from the logs and see if someone else can help.

1 Like
5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.