Skip to content

Configuring SOLR Config Upload

Set the following property only if you are upgrading the self managed from version 8.1.x.x or earlier to 8.7.x.x or a later version.

This guide will help you configure the PORTAL_SOLR_CONFIG_UPLOAD for your Privacera Portal. The PORTAL_SOLR_CONFIG_UPLOAD is a configuration setting that allows you to upload new configurations to SOLR. This setting is crucial for managing and updating your SOLR configurations efficiently.

Why is this Required?

As the SOLR service updates from version solr_8.11.2 to version solr_9.4.0, there are several changes in the configuration files. In the newer version, fundamental components such as managed-schema and solrconfig.xml have been updated. To accommodate these changes, it is necessary to upload the new configurations. This ensures that your SOLR service is running with the latest settings and optimizations, providing better performance and compatibility with the newer version.

Configuring SOLR Config Upload

  1. SSH into the instance where Privacera Manager is installed.

  2. Navigate to the config directory with the following command:

    Bash
    1
    cd ~/privacera/privacera-manager/config

  3. Copy the sample-vars if they are not already present in the custom-vars directory by running the following command:

    Bash
    1
    cp -n sample-vars/vars.portal.yml custom-vars/vars.portal.yml

  4. Update the PORTAL_SOLR_CONFIG_UPLOAD:

    a. Open the vars.portal.yml file in a text editor.

    Bash
    1
    vi custom-vars/vars.portal.yml

    b. Add or update the following property:

    YAML
    1
    PORTAL_SOLR_CONFIG_UPLOAD: true

    c. Save and close the file.

Deploying the Service

  1. Generate the helm charts. This step prepares the necessary Kubernetes configurations for deploying the Privacera services.

    Bash
    1
2
    # This step usually takes a few minutes.
./privacera-manager.sh setup

  2. Apply the helm charts. This will deploy the Privacera services to your Kubernetes cluster. This might take a few minutes.

    Bash
    1
    ./pm_with_helm.sh upgrade

  3. Perform post-installation steps such as generating the Plugin tar ball and updating Route 53 DNS. These steps are necessary to finalize the deployment and ensure that all services are correctly configured.

    Bash
    1
    ./privacera-manager.sh post-install

By following these steps, you will have successfully configured the PORTAL_SOLR_CONFIG_UPLOAD and deployed the Privacera services with the updated configuration.

Disabling SOLR Config Upload

If you need to disable the PORTAL_SOLR_CONFIG_UPLOAD setting after the Privacera Portal is up and running to prevent it from uploading SOLR configs on every restart, follow these steps:

  1. SSH into the instance where Privacera Manager is installed.

  2. Navigate to the config directory with the following command:

    Bash
    1
    cd ~/privacera/privacera-manager/config

  3. Open the vars.portal.yml file in a text editor:

    Bash
    1
    vi custom-vars/vars.portal.yml

  4. Update the PORTAL_SOLR_CONFIG_UPLOAD property to false:

    YAML
    1
    PORTAL_SOLR_CONFIG_UPLOAD: false

  5. Save and close the file.

Deploying the Service

  1. Generate the Helm charts. This step prepares the required Kubernetes configurations for deploying the Privacera services.

    Bash
    1
2
    # This step usually takes a few minutes.
./privacera-manager.sh setup

  2. Apply the Helm charts. This will deploy the Privacera services to your Kubernetes cluster.

    Bash
    1
2
    # This step usually takes a few minutes.
./pm_with_helm.sh upgrade

  3. Perform post-installation steps, such as generating the plugin tarball and updating Route 53 DNS. These steps are essential to finalize the deployment and ensure that all services are properly configured.

    Bash
    1
2
    # This step usually takes a few minutes.
./privacera-manager.sh post-install

By following these steps, you will have successfully disabled the PORTAL_SOLR_CONFIG_UPLOAD setting.

Comments