Aaron Malig
07/02/2026, 8:22 AMRocky
07/02/2026, 8:22 AMstarrocks.http.url parameter to include the https:// prefix and the correct port:
json
{
"name": "starrocks-kafka-connector",
"config": {
"connector.class": "com.starrocks.connector.kafka.StarRocksSinkConnector",
"starrocks.http.url": "https://<fe_host>:8443",
"starrocks.username": "<username>",
"starrocks.password": "<password>",
"starrocks.database.name": "<database_name>",
...
}
}
Important Considerations:
1. Enable HTTPS on FE: Ensure that HTTPS is enabled on your StarRocks FE nodes. In fe.conf, verify that enable_https is set to true (it is false by default in some versions) and the https_port is set to 8443.
2. SSL/TLS Certificates: If your StarRocks cluster uses a self-signed certificate or a certificate from an internal CA, the Java process running Kafka Connect must trust that certificate. You may need to import the FE's certificate into the Java truststore (cacerts) of the Kafka Connect workers:
bash
keytool -import -alias starrocks-fe -file fe_cert.crt -keystore $JAVA_HOME/lib/security/cacerts
3. Multiple FEs: If you have multiple FE nodes, you can provide a comma-separated list:
"starrocks.http.url": "<https://fe1:8443,https://fe2:8443>"
If you encounter a javax.net.ssl.SSLHandshakeException, it typically indicates that the Kafka Connect worker does not trust the FE's SSL certificate.
References
• loading/Kafka-connector-starrocks.md