Version Verification and Planning

Current Version Check

Verify your current Energy Logserver version before planning any upgrade:

curl -u $USER:$PASSWORD -X GET http://localhost:9200/_logserver/license

System Health Pre-Check

curl -u $USER:$PASSWORD "http://localhost:9200/_cluster/health?pretty"

systemctl status logserver logserver-gui logserver-probe intelligence intelligence-scheduler alert license-service skimmer e-doc --no-pager

df -h /usr/share/logserver /var/lib/logserver 2>/dev/null

free -h

System Requirements

Component

Minimum

Recommended

High-Performance

CPU

8 cores

16 cores

32+ cores

Memory

32 GB

64 GB

128+ GB

Storage

500 GB

1 TB SSD

2+ TB NVMe

Network

1 Gbps

10 Gbps

25+ Gbps

Compatibility Matrix

The Compatibility Matrix defines supported upgrade paths to Energy Logserver 8.0. Check your current version before planning an upgrade.

Warning

Upgrading to 8.x requires a full cluster restart. Rolling upgrades are not supported. An upgraded node will not join an existing 7.x cluster.

From Version

Direct Upgrade

Notes

7.4.0 - 7.9.x

Supported

Full cluster restart required. install.sh -u checks index compatibility; indices created on versions older than 7.4.0 must be reindexed or deleted before upgrading.

< 7.4.0

Multi-step

Requires an intermediate upgrade to a version between 7.4.0 and 7.9.0 first, then reindexing incompatible indices, then upgrading to 8.x. Alternatively: fresh 8.x installation and data migration.

7.2.x and below

Unsupported

Complete reinstallation needed

Upgrade Downtime

Warning

Upgrading to 8.x does not support rolling upgrades. All cluster nodes must be stopped and upgraded together.

Single Node Deployment:

  • Downtime: approximately 1 hour

  • Process: Full backup, stop services, run install.sh -u, verify

Multi-Node Cluster:

  • Downtime: depends on cluster size and index count; plan for extended maintenance window

  • Process: Stop all collectors, upgrade the client node first, then the data nodes one by one, answering No to the installer’s restart prompt. Start services manually only after every node has been upgraded. See Multi-node upgrade order for the full procedure.

Rolling upgrades within 7.x:

  • Downtime: 15-30 minutes

  • Process: Node-by-node upgrade with service continuity (only for upgrades within the 7.x release line)