Shut Down Hubble

This is a list of procedures to execute when you want to shutdown/restart the machines that are used by Hubble .

Hubble Application Container (Linux)

Shutting down

1. Login into the Application Server machine through a ssh client (e.g. PuTTY) or your VM host console.
2. Stop our docker services by running the following commands:

   sudo /etc/hubble/stop.sh

3. Power off the machine. You can do that by running:

   shutdown -h now

Starting up

1. Power on the machine.
2. Login into the Application Server machine through a ssh client (e.g. PuTTY) or your VM host console.
3. Make sure all containers are running:

   sudo -i

   /etc/hubble/start.sh

   cd /etc/hubble

   docker-compose ps

All the containers listed should be marked as “Up” (as in the example below):

Note: If you are only restarting the Application server (while the web server is still running) you will have to restart IIS over on the Web server.

Hubble Web Server (Windows)

Shutting down

1. Just power off / restart the machine in the normal way through the OS. All the services should then shutdown without issue.

Starting up

1. Before you power on / restart, the Application services should be up-and-running. After the web server starts up, the InsightYBService should automatically be started and running.
2. If you want to double check, you can do so by making sure Insight YbService process is running:

Hubble Accelerator

Please bear in mind that some of the commands below can take a long time to execute (e.g. stopping the replication tasks, applying changes to Vector). For example, stopping certain replication tasks can take as long as 30 minutes (depending on your setup).    

Shutting down

Step 1: Stop all Replication Tasks from the Replication Console Web Front End

1. If you do not have access to the replication console, login into the Accelerator through VMWare console, directly, or via ssh.
   1. Execute the following command to get a list of all tasks that are currently running:

      /opt/attunity/replicate/bin/repctl gettasklist %

   2. Run the following command substituting <TASK_NAME> with a real task name. This should be repeated for each task returned by step 1:

      /opt/attunity/replicate/bin/repctl connect\; stoptask

      <TASK_NAME>\; disconnect

   3. To confirm all tasks are stopped, execute the following command:

      ps aux | grep 'repctl reptasksrv'

      This should only return the grep command itself.

Step 2: Propagate all In-memory Changes and roll the Changes Log

Important: Propagating the in-memory changes and condensing the log can take some time. It should therefore be planned at a time when it will be least disruptive to the users of the system.

The procedure will fail if in-memory changes are made via queries while it is running. As such, you must ensure that the procedure described in the Step 1, to effectively stop all queries running on the database, has been carried out.

1. Using PuTTY or your preferred terminal window, connect to the accelerator server and login as the root user:
2. Change directory to opt/Actian:

   cd /opt/Actian

3. Switch user to the Accelerator database user:

   su actian

4. To propagate the in-memory changes for all tables in the database run the following command:

   echo "call vectorwise (combine)\g" | sql db

5. After propagating the in-memory changes, the following command should be run to condense the log:

   echo "call vectorwise (condense_log)\g" | sql db

6. Exit from the Actian user:

   exit

Step 3: Turn off the Replication Server

Note: If you see a 'Permission denied' message on the screen you can safely ignore it.

Run the following command:

Step 4: Turn off the Database

Note: If you see a 'Permission denied' message on the screen you can safely ignore it.

Run the following command:

Step 5: Shutdown or Reboot the Machine

Shutdown the machine by running the command:

Reboot the machine by running the command:

Starting up

After the machine boots again, you will need to re-enable all the Qlik tasks. You can do this via the web front-end or by running the following command for each of the tasks (you can re-obtain them by running: /opt/attunity/replicate/bin/repctl gettasklist % ):