14.1 Enabling Scalable Storage Post-Installation

Enabling scalable storage is a one-time configuration, which cannot be reverted. If you want to disable scalable storage and switch to traditional storage, you must re-install Sentinel and not opt for scalable storage during installation.

When you enable scalable storage, the Sentinel server user interface is trimmed down to just cater to scalable data collection, event routing, events dashboard, and other administrator activities. This trimmed down version of Sentinel is referred to as Sentinel Scalable Data Manager (SSDM).

To configure scalable storage:

  1. Complete the prerequisites to enable scalable storage. For information about prerequisites, see Installing and Setting Up Scalable Storage in the Sentinel Installation and Configuration Guide.

  2. From Sentinel Main, click Storage > Scalable Storage.

  3. Select Configure scalable storage.

  4. Specify the IP addresses or hostnames and port numbers of the scalable storage components.

  5. (Conditional) To customize the default configuration of CDH components, click Show advanced configuration.

    If the properties you want to modify are not listed in the user interface, click Add property and set the value.

    Customizing Kafka Configuration

    You can customize the following properties in the Sentinel web interface only when you enable scalable storage for the first time. If you want to modify these properties after scalable storage is enabled, you must use appropriate Kafka tools as mentioned in Kafka documentation. For more information, see Apache Kafka documentation.

    Property

    Recommended Value

    Notes

    default.replication.factor

    2

    Indicates the number of replicas of Kafka partitions, not counting the original copy. For example, for a total of 3 copies of the same partition, a value of 2 means 1 original and 2 replicas.

    num.partitions

    9

    Indicates the number of Kafka topic partitions.

    You can increase this value according to the number of YARN NodeManager vcores. For example: if YARN NodeManager has 16 vcores to utilize, number of Kafka partitions should be 15.

    You can customize other properties at any time as needed.

  6. Click Save.

  7. Log in to the SSDM server.

  8. Redeploy all the Elasticsearch security plug-ins. For steps to redeploy the Elasticsearch plug-in, see Redeploying Elasticsearch Security Plug-In in the Sentinel Installation and Configuration Guide.

  9. Complete CDH and Elasticsearch configuration as mentioned in the following sections: