如何降级EC2服务器中的Vespa引擎版本？（含7.534.29降至7.220.14场景）

Got it, let's walk through exactly how to downgrade your Vespa installation on EC2 from 7.534.29 to 7.220.14. I'll break this down into safe, actionable steps to minimize downtime and risk:

前提准备（必做！） #

Before you start, take these precautions to protect your data and configuration:

• Backup critical data:
  • Copy your Vespa application package (the directory with services.xml, schemas, etc.) to a safe location (like S3 or another EC2 instance).
  • Backup Vespa configuration files: sudo cp -r /etc/vespa /var/tmp/vespa-config-backup
  • If you're using persistent storage for indexes, ensure you have a snapshot or backup of those volumes (EC2 EBS snapshots work great here).
• Confirm your EC2 architecture: You mentioned your current build is linux/amd64—double-check this with uname -m to ensure the 7.220.14 package matches (it will, but better safe than sorry).

具体降级步骤 #

1. Stop the running Vespa service #

First, shut down Vespa cleanly to avoid corrupting data:

sudo systemctl stop vespa
# Verify it's stopped
sudo systemctl status vespa

2. Uninstall the current Vespa version #

Completely remove the existing 7.534.29 installation, including residual files:

For Debian/Ubuntu-based EC2 instances:

sudo apt remove --purge vespa vespa-core vespa-libs vespa-utils -y
# Clean up leftover directories
sudo rm -rf /opt/vespa /var/lib/vespa /var/log/vespa

For RHEL/CentOS-based EC2 instances:

sudo yum remove vespa vespa-core vespa-libs vespa-utils -y
# Clean up leftover directories
sudo rm -rf /opt/vespa /var/lib/vespa /var/log/vespa

3. Configure the Vespa repository for 7.220.x #

You need to point your package manager to the repository hosting the 7.220.14 version:

For Debian/Ubuntu:

First, import the Vespa GPG key (to verify package integrity):

curl -fsSL https://apt.vespa.ai/GPG-KEY-vespa | sudo gpg --dearmor -o /usr/share/keyrings/vespa-archive-keyring.gpg

Then add the 7.220 branch repository:

echo "deb [signed-by=/usr/share/keyrings/vespa-archive-keyring.gpg] https://apt.vespa.ai/ stable 7.220" | sudo tee /etc/apt/sources.list.d/vespa.list
# Update the package index
sudo apt update

For RHEL/CentOS:

Create a dedicated repo file for the 7.220 branch:

sudo tee /etc/yum.repos.d/vespa.repo <<EOF
[vespa]
name=Vespa
baseurl=https://yum.vespa.ai/7.220
gpgcheck=1
gpgkey=https://yum.vespa.ai/GPG-KEY-vespa
EOF
# Clean and update the yum cache
sudo yum clean all && sudo yum makecache

4. Install the exact 7.220.14 version #

Install the specific version you need to avoid accidental upgrades:

For Debian/Ubuntu:

sudo apt install vespa=7.220.14 vespa-core=7.220.14 vespa-libs=7.220.14 vespa-utils=7.220.14 -y

For RHEL/CentOS:

sudo yum install vespa-7.220.14 vespa-core-7.220.14 vespa-libs-7.220.14 vespa-utils-7.220.14 -y

5. Restore your configuration and application #

Bring back your backed-up data:

• Restore configuration files:

  sudo cp -r /var/tmp/vespa-config-backup/* /etc/vespa/
  

• Re-deploy your Vespa application package:

  vespa-deploy prepare /path/to/your/backed-up/app-package
  vespa-deploy activate
  

6. Start Vespa and verify the downgrade #

• Start the service:

  sudo systemctl start vespa
  

• Check the service status:

  sudo systemctl status vespa
  

• Confirm the installed version:

  vespa-version
  

  You should see output like 7.220.14 here.
• Test your custom searcher: Send a few test queries to your Vespa endpoint and check logs for errors:

  # Check Vespa service logs
  journalctl -u vespa -f
  # Or check application-specific logs
  tail -f /var/log/vespa/vespa.log
  

关键注意事项 #

• Index compatibility: Some Vespa versions change index formats. If you're using persistent indexes, verify that 7.220.14 can read the indexes created by 7.534.29. If you run into errors, you may need to reindex your data from scratch.
• Dependency checks: The 7.220.14 version uses an older Go runtime (likely go1.13 or similar), but the Vespa packages include all necessary dependencies—you don't need to install Go separately.
• Downtime: This process requires stopping Vespa, so schedule it during a maintenance window to avoid impacting users.

内容的提问来源于stack exchange，提问作者divyansh