Cloudera Docs

Upgrading CSA artifacts for SQL Stream Builder service

You need to upgrade the Cloudera Streaming Analytics (CSA) artifacts to the newer version by manually deleting the old CSD file from the repository, deactivating the old parcel and installing the latest CSD file and parcel.

  1. Stop the SQL Stream Builder service on your cluster.
    1. Go to your cluster in Cloudera Manager.
    2. Select SQL Stream Builder from the list of services.
    3. Click Action > Stop.
  2. Download the new CSD files from the Download location.
  3. Delete the old CSD version from /opt/cloudera/csd.
    1. Access the host where the CSD is stored. 
      ssh root@<hostname>
cd /opt/cloudera/csd
rm FLINK-1.15.1-csa1.9.0.0-cdh7.1.8.0-801-38169064.jar
rm SQL_STREAM_BUILDER-1.15.1-csa1.9.0.0-cdh7.1.8.0-801-38169064.jar
  4. Copy the new artifacts to the /opt/cloudera/csd folder. 
    scp <download_location>/FLINK-1.16.1-csa1.10.0.0-cdh7.1.8.0-801-41959971.jar root@<hostname>/opt/cloudera/csd:
scp <download_location>/SQL_STREAM_BUILDER-1.16.1-csa1.10.0.0-cdh7.1.8.0-801-41959971.jar root@<hostname>/opt/cloudera/csd:
  5. Ensure that you maintain the appropriate file ownership and access the attributes if needed. 
    chown cloudera-scm:cloudera-scm /opt/cloudera/csd/FLINK-1.16.1-csa1.10.0.0-cdh7.1.8.0-801-41959971.jar
chown cloudera-scm:cloudera-scm /opt/cloudera/csd/SQL_STREAM_BUILDER-1.16.1-csa1.10.0.0-cdh7.1.8.0-801-41959971.jar
  6. Restart the Cloudera Manager Server with the following command:
    • RHEL 7 Compatible, SLES 12, Ubuntu: systemctl restart cloudera-scm-server
    • RHEL 6 Compatible: service cloudera-scm-server restart
  7. Restart the Cloudera Management Services.
    When upgrading from versions lower than CSA 1.7.0:
    Due to the backend changes of SSB, after adding the new CSD, the SSB service will not work which is indicated in the list of services in the following way:
    The following error message is displayed when reviewing the configuration issue:
    This means that you need to manually remove the Streaming SQL Console role, and restart the Streaming SQL Engine role after activating the new parcel.
  8. Select Parcels on the Home > Hosts tab in the Cloudera Manager main navigation bar.
  9. Click on Parcel Repositories & Network Settings tab.
  10. Add the new Remote Parcel Repository URL for CSA. 
    https://user:password@archive.cloudera.com/p/csa/1.10.0.0/parcels/
  11. Click Save & Verify Configuration to commit the change.
  12. Click Close.
    You are redirected to the Parcels page.
  13. Deactivate the old version of the parcel on the Parcels page.
  14. Download, activate and distribute the new version of the parcel.
  15. Select the Activate option when prompted in the wizard.
    For more information about the general process of Service Management, see the Cloudera Manager documentation.
  16. When upgrading from versions lower than CSA 1.7.0:
    Delete the Streaming SQL Console role from your cluster.
    1. Stop the SQL Stream Builder service using Actions > Stop next to the SQL Stream Builder service name.
    2. Select the SQL Stream Builder service.
    3. Select the Streaming SQL Console role.
    4. Click Actions for Selected > Delete.
  17. Update the Admin Database for the SSB service.
    1. Click Actions > Update Admin Database next to the SQL Stream Builder service name.
  18. Create the directory for Job Result Store if you are upgrading from a lower version than CSA 1.8.0.
    1. Select Flink from the list of services.
    2. Click Actions > Create JobResultStore directory.
  19. Start the SQL Stream Builder service.
    1. Click Actions > Start next to the SQL Stream Builder service name.
  20. Refresh your keytab in Streaming SQL Console.
    1. Select SQL Stream Builder from the list of services.
    2. Click SQLStreamBuilder Console.
      The Streaming SQL Console opens in a new window.
    3. Select your username on the left main menu of Streaming SQL Console.
    4. Click Manage keytab.
    5. Provide your password again.
    6. Click Refresh Keytab.
  21. Update the value for the Project ID in case the Organization ID was customized.

    If a default organization ID was configured with a custom value in CSA 1.9.0 or in a lower version, the same value must be added to the default Project ID after upgrading to CSA 1.10.0, because the Streaming SQL Engine will fail to start.