Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Nifi - Confluent Schema Registry cluster - no failover to second URL by processors using the schema registry service?

Nifi - Confluent Schema Registry cluster - no failover to second URL by processors using the schema registry service?

New Contributor

Hi,

We are using the Confluent Schema Registry, and have two instances running on two separate servers by way of HA. I have defined the Controller Service with two comma-separated URLs

109485-confluent-schema-registry-definition.png


The problem we encounter, is the processors that use this controller service don't seem to switch between the schema-registry urls when one server goes down e.g. if a data flow is running and I switch of the schema registry on one server, the processors throw a bulletin stating it cannot find the schema definition, they don't automatically try the second URL. Is this automated-failover meant to occur?


Thanks,

Tama