HI Team. While upgrading datahub from 0.9.6.1 -&gt...
# all-things-deployment
n
HI Team. While upgrading datahub from 0.9.6.1 -> 0.10.0, I 've got this errors. Could you help me to solve this errors?
Copy code
2023-07-20 10:03:44,515 [ThreadPoolTaskExecutor-1] ERROR o.s.k.l.KafkaMessageListenerContainer$ListenerConsumer:149 - Consumer exception                                         │
│ java.lang.IllegalStateException: This error handler cannot process 'SerializationException's directly; please consider configuring an 'ErrorHandlingDeserializer' in the value a │
│ nd/or key deserializer                                                                                                                                                           
│     at org.springframework.kafka.listener.SeekUtils.seekOrRecover(SeekUtils.java:194)                                                                                            
│     at org.springframework.kafka.listener.SeekToCurrentErrorHandler.handle(SeekToCurrentErrorHandler.java:112)                                                                   
│     at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.handleConsumerException(KafkaMessageListenerContainer.java:1604)                        
│     at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.run(KafkaMessageListenerContainer.java:1212)                                            
│     at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)                                                                                         
│     at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)                                                                                                        
│     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)                                                                                 
│     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)                                                                                 
│     at java.base/java.lang.Thread.run(Thread.java:829)                                                                                                                           
│ Caused by: org.apache.kafka.common.errors.SerializationException: Error deserializing key/value for partition DataHubUpgradeHistory_v1-0 at offset 11. If needed, please seek pa │
│ st the record to continue consumption.                                                                                                                                           
│ Caused by: org.apache.kafka.common.errors.SerializationException: Error retrieving Avro unknown schema for id 1                                                                  
│ Caused by: io.confluent.kafka.schemaregistry.client.rest.exceptions.RestClientException: Schema not found; error code: 40403
1
d
That's strange - @brainy-tent-14503 might be able to speak to this. In the meantime, could you try the steps in the thread and share how it goes? : https://datahubspace.slack.com/archives/CV2UVAPPG/p1686819437596959?thread_ts=1686666493.198569&cid=CV2UVAPPG
n
Thanks Hyejin. I'm gonna follow steps based on the thread
I've used this command
Copy code
helm upgrade -i datahub datahub/datahub \
  --debug \
  --timeout 10m \
  --wait \
  --version 0.2.179 \
  --set datahub-gms.image.tag="v0.10.4" \
  --set datahub-frontend.image.tag="v0.10.4" \
  --set elasticsearchSetupJob.image.tag="v0.10.4" \
  --set datahubUpgrade.image.tag="v0.10.4" \
  --values ./datahub.helm-config.yaml
datahub-gms in
datahub.helm-config.yaml
I've pick extraEnvs out
Copy code
datahub-gms:
  enabled: true
  image:
    repository: linkedin/datahub-gms
  service:
    type: ClusterIP
b
Yeah, that initial error is related to duplicate environment variables, likely one or more of them have been moved into helm chart values instead of having to set them in extraEnvs. @nice-xylophone-16750 - were you able to then deploy successfully?
n
Hi @brainy-tent-14503 🙂 After facing this errors several times, I uninstalled the datahub from helm chart. I installed the 0.10.4 version again. Then, this issue disappeared