Cluster upgrade

    1. Restart the BE node and check the BE log be.INFO to see if the boot was successful.
    2. If the startup fails, you can check the reason first. If the error is not recoverable, you can delete the BE directly through DROP BACKEND, clean up the data, and restart the BE using the previous version of palo_be. Then re-ADD BACKEND. (This method will result in the loss of a copy of the data, please make sure that three copies are complete, and perform this operation!!!
    1. Important! Exceptional metadata compatibility is likely to cause data cannot be restored!!
    2. Deploy a test FE process (such as your own local developer) using the new version alone.
    3. Modify the FE configuration file fe.conf for testing and set all ports to different from online.
    4. Add configuration in fe.conf: cluster_id=123456
    5. Add the configuration in fe.conf: metadatafailure_recovery=true
    6. Copy the metadata directory palo-meta of the online environment Master FE to the test environment
    7. “27979;” “35797;” “3681616;” sh bin /start fe.sh “21551;” FE
    8. Observe whether the start-up is successful through FE log fe.log.
    9. If the startup is successful, run sh bin/stop_fe.sh to stop the FE process of the test environment.
    10. The purpose of the above 2-6 steps is to prevent the FE of the test environment from being misconnected to the online environment after it starts.
    1. After data validation, the new version of BE and FE binary files are distributed to their respective directories.
    2. Usually small version upgrade, BE only needs to upgrade palo_be; FE only needs to upgrade palo-fe.jar. If it is a large version upgrade, you may need to upgrade other files (including but not limited to bin / lib / etc.) If you are not sure whether you need to replace other files, it is recommended to replace all of them.
    1. Confirm that the new version of the file is deployed. Restart FE and BE instances one by one.
    2. It is suggested that BE be restarted one by one and FE be restarted one by one. Because Doris usually guarantees backward compatibility between FE and BE, that is, the old version of FE can access the new version of BE. However, the old version of BE may not be supported to access the new version of FE.