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

Manually setting time via EXAoperation

    XMLWordPrintable

    Details

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


      This article guides you through the procedure of setting the time on clusters manually as preparation of configuring NTP servers (SOL-331).

      Please note that

      1. The cluster nodes constantly exchange configuration and vitality information and depend on proper time synchronsiation. While it is possible to manually set the time on EXASolution clusters, it is highly recommended to supply NTP servers for time synchronisation.
      2. The update requires a maintenance window of at least half an hour.
      3. The tasks performed in EXAoperation requires a user with at least "Administrator" privileges.

      Procedure

      1.1. Shutdown all databases

      • Open 'Services > EXASolution'
      • Check the database operations. If the database is stopped while an operation is in progress the operation will be aborted
      • Select all (running) EXASolution instances
      • Click on the button "Shutdown"
      • Reload the page until all instances change their status from "Running" to "Created"
      • You may follow the procedure in an appropriate logservice:

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

      1.2 Shutdown EXAStorage Service

      • Open 'Service > EXAStorage'
      • Check if any operations are currently in progress (if EXAStorage is stopped while an operation is in progress, the operation will be aborted)
      • Click on button "Shutdown Storage Service"
      • After successfull shutdown, the EXAStorage page displays:

      1.3 Check NTP configuration

      • Open 'Configuration > Network'
      • Check if there are already ntp servers configured. If yes please remove them by clicking on "Edit".
      • Open 'Service > Monitoring'
      • Change the time
      • Click on "Set Cluster time"

        Please follow the instruction of SOL-331. See "Procedure - 1.2 Configure NTP server & 1.3 Synchronise time on the cluster"

      1.4 Startup storage

      • 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

      1.5 Startup database

      • Open the Services > EXASolution page and repeat the following steps for all instances:
      • Click on an EXASolution instance name
      • 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.

      Show
      This article guides you through the procedure of setting the time on clusters manually as preparation of configuring NTP servers ( SOL-331 ). Please note that The cluster nodes constantly exchange configuration and vitality information and depend on proper time synchronsiation. While it is possible to manually set the time on EXASolution clusters, it is highly recommended to supply NTP servers for time synchronisation. The update requires a maintenance window of at least half an hour. The tasks performed in EXAoperation requires a user with at least "Administrator" privileges. Procedure 1.1. Shutdown all databases Open 'Services > EXASolution' Check the database operations. If the database is stopped while an operation is in progress the operation will be aborted Select all (running) EXASolution instances Click on the button "Shutdown" Reload the page until all instances change their status from "Running" to "Created" You may follow the procedure in an appropriate logservice: System marked as stopped. Successfully send retry shutdown event to system partition 64. EXASolution exa_db is rejecting connections controller-st(0.0): Shutdown called. User 0 requests shutdown of system. 1.2 Shutdown EXAStorage Service Open 'Service > EXAStorage' Check if any operations are currently in progress (if EXAStorage is stopped while an operation is in progress, the operation will be aborted) Click on button "Shutdown Storage Service" After successfull shutdown, the EXAStorage page displays: 1.3 Check NTP configuration Open 'Configuration > Network' Check if there are already ntp servers configured. If yes please remove them by clicking on "Edit". Open 'Service > Monitoring' Change the time Click on "Set Cluster time" Please follow the instruction of SOL-331 . See "Procedure - 1.2 Configure NTP server & 1.3 Synchronise time on the cluster" 1.4 Startup storage 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 1.5 Startup database Open the Services > EXASolution page and repeat the following steps for all instances: Click on an EXASolution instance name 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.
    • Category 1:
      Cluster Administration - Monitoring & Logging
    • Category 2:
      Cluster Administration - Cluster Management

      Attachments

        Issue Links

        1. 1.1.3_shutdown_db_2.png
          58 kB
        2. 1.2.1_check_storage_operations.png
          99 kB
        3. 1.2.2_shutdown_storage.png
          99 kB
        4. 1.1.1_check_database_operations.png
          59 kB
        5. 1.1.2_shutdown_db.png
          59 kB
        6. 1.2.3_shutdown_storage2.png
          64 kB
        7. 1.3.1_check_ntp.png
          76 kB
        8. 1.3.2_set_time.png
          83 kB
        9. 1.4.1_edit_network.png
          76 kB
        10. 1.5.1_start_database-1.png
          53 kB
        11. 1.5.2_start_database-2.png
          30 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: