How to quickly upgrade the heavydb6.4 version to heavydb7.0 online? 

Follow

jieguo

• October 07, 2023 08:14

How to quickly upgrade the heavydb6.4 version to heavydb7.0 online? The premise is that hundreds of gigabytes of data already exist in the database. Please give us the reference document. Thank you.

0

• 

  Candido Dessanti

  • October 09, 2023 12:17

  Hi jieguo,
  
  You can find the documents on upgrading the 6.x suite to 7.x in our documentation at this link:

  Upgrade Documentation.

  If you wish to ensure the ability to revert to the 6.x release, please take a backup of your current data directory before proceeding with the upgrade process.

  Thank you.

  
  
  
  

  0

  Comment actions Permalink
• 

  jieguo

  • October 10, 2023 02:33

  I made a backup according to the documentation and installed 7.0. after the backup data directory was replaced by the /var/lib/heavydb/storage directory, it failed to start the service.

   

  you can see:

  startHeavyDBServer
  Check failed: cat 

   

  

  0

  Comment actions Permalink
• 

  Candido Dessanti

  • October 31, 2023 10:28

  Hi,

   

  so if I understand everything correctly, you did the following steps

  1. Stopped the container
  2. Performed a backup of the existing data, replicating the 6.4 data into the path /var/lib/heavyai-7.0/storage7.0-6.4
  3. Started a new container containing the update version of software (let's say 7.0) mapping the /var/lib/heavyai/storage to /var/lib/heavyai-7.0/storage7.0-6.4

  Candido

  0

  Comment actions Permalink
• 

  jieguo

  • November 01, 2023 03:21

  Yes,I followed your step ，but failed to start. Can you test it?

  

  0

  Comment actions Permalink
• 

  Candido Dessanti

  • November 02, 2023 22:12

  Hi,
  
  I migrated from 6.x to 7.x several times without having any issue like that, but I never renamed the storage directory, especially with  a  docker image that uses a fixed internal heavyai base. 
  
  I usually stop the docker, then I take a backup with an OS utility like tar, and after that I run a different version of the docker without renaming any directory.
  
  I'll try that approach, but it looks like something related to docker disk mapping.
  
  Candido

   

  0

  Comment actions Permalink

Please sign in to leave a comment.