Configuring RMI JMX with Basic Authentication

To collect Java Management Extensions (JMX) data through a Remote Method Invocation (RMI) port that's secured with Basic Authentication, follow these steps:

  1. Create the Override Configuration File (if it doesn't exist): Navigate to your cluster's directory and create an override.yml file if one isn't already present:
Bash
Copy
  1. Configure the override.yml File:
    1. Open the override.yml file using a text editor:
Bash
Copy

b. Insert the following configurations for the respective services, if they're not already included:

  • For Hive Metastore:
Bash
Copy
  • For Hive Server:
Bash
Copy
  • For Kafka:
Bash
Copy
  • For Zeppelin:
Bash
Copy
  • For Zookeeper:
Bash
Copy
  • For Kafka Mirror Maker:
Bash
Copy

c. Save your changes to the override.yml file.

d. Apply the new configuration by running the following command:

Bash
Copy

Configuring SSL for JMX RMI Port

To gather JMX data through an Secure Sockets Layer (SSL)-enabled RMI port, ensure the following procedure is adhered to, keeping in mind that all SSL certificates (truststores) must be identical across services with exposed JMX RMI ports.

  1. Create the Override Configuration File: If the override.yml file doesn't exist within your cluster's workspace, create it:
Bash
Copy
  1. Configure the override.yml File:

a. Open the override.yml file for editing:

Bash
Copy

b. Add the necessary SSL configuration for each specific service if not already present. Begin with the common configuration applicable to all services:

  • Common Configuration for All Services:
Bash
Copy
  • For Hive Metastore:
Bash
Copy
  • For Hive Server:
Bash
Copy
  • For Zeppelin:
Bash
Copy
  • For Zookeeper:
Bash
Copy
  • For Kafka Mirror Maker:
Bash
Copy

c. Save the changes to the override.yml file.

d. Apply the new SSL configurations by running:

Bash
Copy
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard