Uploaded image for project: 'Solution Center'
  1. Solution Center
  2. SOL-567

How to update a minor version (Version 5 or 6)

    Details

    • Type: How To
    • Status: Published
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: EXASolution
    • Labels:
      None
    • Solution:
      Hide

      Synopsis

      This article guides you through the minor update procedure from a EXASuite version 5.0.X or version 6.0.X.
      This 'How To' article provides you with instructions on how to update from version 5.0.9 to 5.0.11 instance.

       

      Please note that

      # The update requires a maintenance window of at least one hour

      1. The tasks performed in EXAoperation require a user with at least "Administrator" privileges
      2. It is vital to wait for uploads and reboots to finish completely
      3. It's highly recommended to create a current backup before the procedure will be executed.

       

      Applicability

      This solution is applicable to all minor versions above 5.0.3.

       

      Installation instructions

      1. Check Software Versions
      • Open Configuration > Software in EXAoperation and click on the tab "Versions"
      2. EXAoperation master node
      • The update must be applied to a real license server since it is the only node that boots from the local hard drive.
      • Check the following things:
        • In EXAoperation, please navigate to Configuration > Network
        • Open the tab "System"
        • Ensure that the license server (usually node n0010) is listed as "License Server Node"
      • Move EXAoperation if the license server is not the "License Server Node":
        • Open the Page Services > EXAoperation
        • Select "n0010" from the dropdown list
        • Confirm with the click on the button "Move to specified Node"
        • Return to the Configuration > Network page and examine if the license server is now the EXAoperation master
      3. Check database operation
      • Navigate to the EXAoperation page Services > EXASolution
      • Review the database list and check if the column "Background Restore" indicates "None" on all instances
      4. Shutdown all databases
      • Open the Services > EXASolution page
      • Select all (running) EXASolution instances
      • Click on the button "Shutdown"
      • Reload the page until all instances change their status from "Running" to "Created"
      • Again, you may follow the procedure in an appropriate logservice:

        System marked as stopped.
        Successfully send retry shutdown event to system partition 64.
        EXASolution DEMO is rejecting connections
        controller-st(0.0): Shutdown called.
        User 0 requests shutdown of system.

        5. Shutdown EXAStorage
      • Navigate to the EXAoperation page Services > EXAStorage
      • Click on the button "Shutdown Storage Service" and confirm your choice when prompted. When the storage service is down, it looks like in the image below:
      6. Suspend Nodes
      • Open the Configuration > Nodes page in EXAoperation
      • Select all nodes in the tab "Cluster Nodes"
      • Select "Stop cluster services" from actions dropdown menu
      • Confirm with click on the button "Execute"
      • Reload the page and until all nodes indicate the State/Op. "Suspended"

        The 2nd state of every node must be "Active"! Restarting a node which is on "To Install" state will lead into an unrecoverable data loss!

      7. Upload EXASuite 5.0.11
      • Open the Configuration > Software page in EXAoperation
      • In the tab "Versions" please find the input box labelled "Software Update File:"
      • Click on the button "Browse" (label depends on browser, language and operating system)
      • Choose "EXAClusterOS-5.0.11_LS-Update.pkg" in the newly opened file selector
      • Confirm by clicking on the button "Submit" and wait until EXAoperation displays the message:

        First part of update process succeeded. Please shutdown databases, Storage and nodes and restart license server.

      • On the EXAoperation Services > Monitoring page you may open an appropriately defined logservice that will present a messages similar to:

        Start update process to EXAClusterOS version 5.0.11.
        Current kernel is more recent than required kernel. Do not install required kernel.
        First part of update process succeeded. Please shutdown databases and nodes and restart license server.

      8. Reboot the license server
      • Open the Configuration > Nodes page in EXAoperation
      • Navigate down to the section "License Nodes"
      • Click on the button "Reboot" next to the license server (usually node n0010)
      • If reboot is not possible, you may open the license server console (e.g. in iDRAC or vSphere) and send the key sequence CTRL + ALT + DEL.
      • Wait for the license server to finish it's startup procedure (about 15 to 25 minutes) and log into EXAoperation again.
      9. Check Software Versions
      • Open Configuration > Software in EXAoperation and click on the tab "Versions"
      • The field labelled EXAClusterOS must now present version "5.0.11"
      10. Reboot the database nodes
      • Navigate to the Configuration > Nodes page
      • Select all nodes in the tab "Cluster Nodes"
      • Choose "Reboot" from actions dropdown menu and confirm with click on button "Execute"
      • Wait for the nodes to finish reboot (about 15 to 25 minutes)
      • Reload the nodes page until the State/Op. column changes from "booting" to "running" for all nodes
      • You may watch the boot process (of node n11 in this example) in an appropriately configured logservice:
        client ID is '27.1.0.16'
        Client version is '5.0.9'
        Client mac adress is '00:11:22:33:44:55'
        Initialize boot process.
        Client mac address of eth0 matches the expected value (00:11:22:33:44:55)
        Client mac address of eth1 matches the expected value (00:12:34:56:78:9A)
        Mount hard drives.
        Hard drives mounted.
        Prepare boot process stage 3.
        Node does not support CPU power management (requested 'performance').
        Successfully unpacked package on client node: EXAClusterOS-5.0.11_CentOS-6.5_x86_64.tar.gz
        Successfully unpacked package on client node: EXARuntime-5.0.11_x86_64.tar.gz
        Successfully updated kernel packages.
        Successfully synchronized EXAoperation.
        Successfully updated EXAStorage metadata.
        Successfully unpacked package on client node: EXASolution-5.0.11_x86_64.tar.gz
        Successfully unpacked package on client node: EXASolution-5.0.11-COS-5.0.11_x86_64.tar.gz
        Successfully unpacked package on client node: JDBC_Drivers-2014-03-05.tar.gz
        Successfully unpacked package on client node: java-package-2014-04-29.tar.gz
        Successfully initialized thresholds for node monitoring
        Start boot process stage 3.
        Boot process stage 3 finished.
        Boot process stages 1 to 3 took 833 seconds.
      11. Startup EXAStorage
      • Navigate to the EXAoperation page Services > EXAStorage
      • Ensure that all database nodes indicates the state "Running"
      • Click on the button "Startup Storage Service" and confirm your choice when prompted
      • After the EXAStorage page has been reloaded, check the status of all nodes, disks and volumes
      12. Update and start the databases
      • Open the Services > EXASolution page and repeat the following steps for all instances:
      • Click on an EXASolution instance name to open the properties page
      • Click on the button "Edit" on the bottom of the page to open the "Edit Database" form
      • Select "5.0.9" from the dropdown menu labelled "Version" and confirm with click on the button "Apply"
      • You will be redirected to the EXASolution instance properties page
      • From the "Actions" dropdown menu please select "Startup" and confirm with click on the button "Submit".
      • Navigate back to the Services > EXASolution page and reload until the database indicates the status "Running"
      • You may follow the procedure in an appropriate logservice:
        EXASolution exa_demo is accepting connections
        System is ready to receive client connections.
        System started successfully in partition 44.
        User 0 requests startup of system.
        User 0 requests new system setup.
      13. Start EXAoperation plugins

      If required, you may start services delivered through EXAoperaton plugins (XML-RPC) now.

      Show
      Synopsis This article guides you through the minor update procedure from a EXASuite version 5.0.X or version 6.0.X. This 'How To' article provides you with instructions on how to update from version 5.0.9 to 5.0.11 instance.   Please note that # The update requires a maintenance window of at least one hour The tasks performed in EXAoperation require a user with at least "Administrator" privileges It is vital to wait for uploads and reboots to finish completely It's highly recommended to create a current backup before the procedure will be executed.   Applicability This solution is applicable to all minor versions above 5.0.3.   Installation instructions 1. Check Software Versions Open Configuration > Software in EXAoperation and click on the tab "Versions" 2. EXAoperation master node The update must be applied to a real license server since it is the only node that boots from the local hard drive. Check the following things: In EXAoperation, please navigate to Configuration > Network Open the tab "System" Ensure that the license server (usually node n0010) is listed as "License Server Node" Move EXAoperation if the license server is not the "License Server Node": Open the Page Services > EXAoperation Select "n0010" from the dropdown list Confirm with the click on the button "Move to specified Node" Return to the Configuration > Network page and examine if the license server is now the EXAoperation master 3. Check database operation Navigate to the EXAoperation page Services > EXASolution Review the database list and check if the column "Background Restore" indicates "None" on all instances 4. Shutdown all databases Open the Services > EXASolution page Select all (running) EXASolution instances Click on the button "Shutdown" Reload the page until all instances change their status from "Running" to "Created" Again, you may follow the procedure in an appropriate logservice: System marked as stopped. Successfully send retry shutdown event to system partition 64. EXASolution DEMO is rejecting connections controller-st(0.0): Shutdown called. User 0 requests shutdown of system. 5. Shutdown EXAStorage Navigate to the EXAoperation page Services > EXAStorage Click on the button "Shutdown Storage Service" and confirm your choice when prompted. When the storage service is down, it looks like in the image below: 6. Suspend Nodes Open the Configuration > Nodes page in EXAoperation Select all nodes in the tab "Cluster Nodes" Select "Stop cluster services" from actions dropdown menu Confirm with click on the button "Execute" Reload the page and until all nodes indicate the State/Op. "Suspended" The 2nd state of every node must be "Active"! Restarting a node which is on "To Install" state will lead into an unrecoverable data loss! 7. Upload EXASuite 5.0.11 Open the Configuration > Software page in EXAoperation In the tab "Versions" please find the input box labelled "Software Update File:" Click on the button "Browse" (label depends on browser, language and operating system) Choose "EXAClusterOS-5.0.11_LS-Update.pkg" in the newly opened file selector Confirm by clicking on the button "Submit" and wait until EXAoperation displays the message: First part of update process succeeded. Please shutdown databases, Storage and nodes and restart license server. On the EXAoperation Services > Monitoring page you may open an appropriately defined logservice that will present a messages similar to: Start update process to EXAClusterOS version 5.0.11. Current kernel is more recent than required kernel. Do not install required kernel. First part of update process succeeded. Please shutdown databases and nodes and restart license server. 8. Reboot the license server Open the Configuration > Nodes page in EXAoperation Navigate down to the section "License Nodes" Click on the button "Reboot" next to the license server (usually node n0010) If reboot is not possible, you may open the license server console (e.g. in iDRAC or vSphere) and send the key sequence CTRL + ALT + DEL. Wait for the license server to finish it's startup procedure (about 15 to 25 minutes) and log into EXAoperation again. 9. Check Software Versions Open Configuration > Software in EXAoperation and click on the tab "Versions" The field labelled EXAClusterOS must now present version "5.0.11" 10. Reboot the database nodes Navigate to the Configuration > Nodes page Select all nodes in the tab "Cluster Nodes" Choose "Reboot" from actions dropdown menu and confirm with click on button "Execute" Wait for the nodes to finish reboot (about 15 to 25 minutes) Reload the nodes page until the State/Op. column changes from "booting" to "running" for all nodes You may watch the boot process (of node n11 in this example) in an appropriately configured logservice: client ID is '27.1.0.16' Client version is '5.0.9' Client mac adress is '00:11:22:33:44:55' Initialize boot process. Client mac address of eth0 matches the expected value (00:11:22:33:44:55) Client mac address of eth1 matches the expected value (00:12:34:56:78:9A) Mount hard drives. Hard drives mounted. Prepare boot process stage 3. Node does not support CPU power management (requested 'performance'). Successfully unpacked package on client node: EXAClusterOS-5.0.11_CentOS-6.5_x86_64.tar.gz Successfully unpacked package on client node: EXARuntime-5.0.11_x86_64.tar.gz Successfully updated kernel packages. Successfully synchronized EXAoperation. Successfully updated EXAStorage metadata. Successfully unpacked package on client node: EXASolution-5.0.11_x86_64.tar.gz Successfully unpacked package on client node: EXASolution-5.0.11-COS-5.0.11_x86_64.tar.gz Successfully unpacked package on client node: JDBC_Drivers-2014-03-05.tar.gz Successfully unpacked package on client node: java-package-2014-04-29.tar.gz Successfully initialized thresholds for node monitoring Start boot process stage 3. Boot process stage 3 finished. Boot process stages 1 to 3 took 833 seconds. 11. Startup EXAStorage Navigate to the EXAoperation page Services > EXAStorage Ensure that all database nodes indicates the state "Running" Click on the button "Startup Storage Service" and confirm your choice when prompted After the EXAStorage page has been reloaded, check the status of all nodes, disks and volumes 12. Update and start the databases Open the Services > EXASolution page and repeat the following steps for all instances: Click on an EXASolution instance name to open the properties page Click on the button "Edit" on the bottom of the page to open the "Edit Database" form Select "5.0.9" from the dropdown menu labelled "Version" and confirm with click on the button "Apply" You will be redirected to the EXASolution instance properties page From the "Actions" dropdown menu please select "Startup" and confirm with click on the button "Submit". Navigate back to the Services > EXASolution page and reload until the database indicates the status "Running" You may follow the procedure in an appropriate logservice: EXASolution exa_demo is accepting connections System is ready to receive client connections. System started successfully in partition 44. User 0 requests startup of system. User 0 requests new system setup. 13. Start EXAoperation plugins If required, you may start services delivered through EXAoperaton plugins (XML-RPC) now.
    • Category 1:
      Cluster Administration - Update

      Attachments

      1. 1_check_software_versions.png
        1_check_software_versions.png
        67 kB
      2. 10_reboot_database_nodes.png
        10_reboot_database_nodes.png
        125 kB
      3. 12_update_and_start_database-1.png
        12_update_and_start_database-1.png
        53 kB
      4. 12_update_and_start_database-2.png
        12_update_and_start_database-2.png
        29 kB
      5. 12_update_and_start_database-3.png
        12_update_and_start_database-3.png
        30 kB
      6. 2_check_exaoperation_master.png
        2_check_exaoperation_master.png
        83 kB
      7. 2_move_exaoperation_master.png
        2_move_exaoperation_master.png
        46 kB
      8. 3_check_database_operation.png
        3_check_database_operation.png
        58 kB
      9. 5_shutdown_all_databases-1.png
        5_shutdown_all_databases-1.png
        62 kB
      10. 5_shutdown_all_databases-2.png
        5_shutdown_all_databases-2.png
        54 kB
      11. 6_shutdown_exastorage-1.png
        6_shutdown_exastorage-1.png
        104 kB
      12. 6_shutdown_exastorage-2.png
        6_shutdown_exastorage-2.png
        58 kB
      13. 7_suspend_nodes-1.png
        7_suspend_nodes-1.png
        94 kB
      14. 7_suspend_nodes-2.png
        7_suspend_nodes-2.png
        129 kB
      15. 7_upload_exasuite_5011.png
        7_upload_exasuite_5011.png
        74 kB
      16. 7_upload_exasuite_5011-2.png
        7_upload_exasuite_5011-2.png
        75 kB
      17. 8_reboot_licenseserver_exaoperation.png
        8_reboot_licenseserver_exaoperation.png
        78 kB
      18. 9_check_software_version.png
        9_check_software_version.png
        66 kB

        Activity

          People

          • Assignee:
            CaptainEXA Captain EXASOL
            Reporter:
            CaptainEXA Captain EXASOL
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: