Managing the index cluster

The index is the main element of Qlik Associative Big Data Index, containing indexlets that are persisted data and symbol tables representing the big data. You need to create the index by executing the supplied shell scripts in the cluster.

Managing cluster settings

Information about the nodes of the cluster is maintained in the configuration file cluster.json, which is located in the home/ubuntu/dist/runtime/config folder.

This file is generated automatically by the update_config_json.sh script when the indexing cluster is deployed. You can update IP addresses of nodes if they need to be changed after the deployment.

Managing the indexing services

You can list, start or stop the indexing services by running the service_manager.sh located in the /runtime/scripts/indexer folder. The script will manage all services that are configured in the cluster.json and indexing_setting.json configuration files.

Example:  

./service_manager.sh

The script will start in interactive mode with the following options:

Option Description
h Print help for the script
1 List all indexing services that are running.
2 Stop an indexing service.
3 Start an indexing service.
a

Stop all indexing services.

q Quit

Starting and stopping Qlik Associative Big Data Index services

We recommend that you use the available shell scripts for both starting and stopping the Qlik Associative Big Data Index services. It is possible to login to the QSL and Indexer environments and kill the processes, but there are dependencies to consider, and the services must be started in the correct order.

Starting the services

When starting the environment, start the Indexer services first, and then the QSL services.

~/dist/runtime/scripts/indexer/start_indexing_env.sh
~/dist/runtime/scripts/qsl_processor/start_qsl_env.sh

Stopping the services

When stopping the environment, it is equally as important to first stop the QSL services, and then the Indexer services.

~/dist/runtime/scripts/qsl_processor/stop_qsl_env.sh

~/dist/runtime/scripts/indexer/service_manager.sh (Use option a)

Collecting logs from the Qlik Associative Big Data Index environment

Troubleshooting may be needed when the index cluster does not behave as expected (for example, if the system responds with an error message that needs further investigation or does not respond at all when an error occurs). The log messages provide important information that can be used to detect problems in the environment.

Qlik Associative Big Data Index logs are saved in the indexing output folder. The exact path depends on your configuration settings.

Example:  

/mnt/efs/<user>/indexing/output/logs

If you want to collect the logs, you need to upload them to a shared location that you can access outside the Qlik Associative Big Data Index environment. We recommend that you upload the logs to your AWS Qlik Associative Big Data Index bucket (<s3 bucket path> in the example):

Note: This requires that a zip tool is installed in the environment.
sudo apt install zip cd /mnt/efs/<user>/indexing/output/logs Zip –r MyLogs.zip *.* aws s3 cp logs.zip s3://<s3 bucket path>/
 

When you have uploaded the zipped log files, switch to your personal environment outside Qlik Associative Big Data Index and download the files from the AWS Qlik Associative Big Data Index bucket.

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?