@dazzling-judge-80093 / @gray-shoe-75895, We are running into a issue where our Glossary Terms not showing up datasets in “Related Entities” page and throwing a 500. Here are details around ingestion. 1) ingested glossary terms through yaml 2) ingested s3 objects from CLI 3) used CSV enricher to add terms to columns. Term in question has a parent glossaryNode. Cc: @billowy-book-26360

analyzer [custom_keyword] not found

@echoing-airport-49548 does that error message mean anything to you?

When tried restoring Elastic search index through cron job notified this error

I’m not familiar with this search error

Is this related to Kafka message request size? How do we increase this

I’m checking with my colleagues and I can get back to you cc @big-carpet-38439

Hi @little-breakfast-38102 to fix the second image you posted, you need to increase the kafka message payload size in the datahub helm chart.

SPRING_KAFKA_PRODUCER_PROPERTIES_MAX_REQUEST_SIZE

Note that the equivalent config must be made on Kafka. Essentially Kafka needs to support large payloads in each message.

Cc: @square-eye-43731

The variable is not explicitly set anywhere but is accepted by spring which gms uses.