Hi team, i’ve passed custom topic names as extraEn...
# all-things-deployment
b
Hi team, i’ve passed custom topic names as extraEnvs in Helm values to
datahub-gms
, but still got below error
Copy code
13:54:26.103 [main] ERROR o.s.web.context.ContextLoader - Context initialization failed
org.springframework.context.ApplicationContextException: Failed to start bean 'org.springframework.kafka.config.internalKafkaListenerEndpointRegistry'; nested exception is java.lang.IllegalStateException: Topic(s) [MetadataChangeEvent_v4] is/are not present and missingTopicsFatal is true
	at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:185)
	at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:53)
	at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:360)
	at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:158)
Do you have some idea?
plus1 1
b
@early-lamp-41924 does this setup look good?
e
Hi Harvey. Unfortunately, there are a few more env that you need to set because the env names for mae/mce consumers are different. Here is the full list
Copy code
- name: METADATA_CHANGE_EVENT_NAME
              value: {{ .metadata_change_event_name }}
            - name: FAILED_METADATA_CHANGE_EVENT_NAME
              value: {{ .failed_metadata_change_event_name }}
            - name: METADATA_AUDIT_EVENT_NAME
              value: {{ .metadata_audit_event_name }}
            - name: KAFKA_TOPIC_NAME
              value: {{ .metadata_audit_event_name }}
            - name: KAFKA_MCE_TOPIC_NAME
              value: {{ .metadata_change_event_name }}
            - name: KAFKA_FMCE_TOPIC_NAME
              value: {{ .failed_metadata_change_event_name }}
            - name: DATAHUB_USAGE_EVENT_NAME
              value: {{ .datahub_usage_event_name }}
            - name: METADATA_CHANGE_PROPOSAL_TOPIC_NAME
              value: {{ .metadata_change_proposal_topic_name }}
            - name: FAILED_METADATA_CHANGE_PROPOSAL_TOPIC_NAME
              value: {{ .failed_metadata_change_proposal_topic_name }}
            - name: METADATA_CHANGE_LOG_VERSIONED_TOPIC_NAME
              value: {{ .metadata_change_log_versioned_topic_name }}
            - name: METADATA_CHANGE_LOG_TIMESERIES_TOPIC_NAME
              value: {{ .metadata_change_log_timeseries_topic_name }}
b
Thanks both! Managed to bring up Datahub with our internal Kafka & ES!
b
W00hoo!
Let us know if you face anything else 😛
thankyou 1