MCE Consumer Errors in Logs

System logs showed a high volume of errors in the MCE (Metadata Change Event) consumer, indicating problems processing incoming metadata events. These errors could lead to metadata ingestion failures, delays in metadata propagation, or inconsistent state across the platform.

Common Error Messages:

• MCE consumer processing errors
• Failed to process metadata change event
• Event deserialization failures

The MCE consumer has been improved to better handle edge cases in event processing. The fixes address issues with: - Event format validation - Schema compatibility checking - Error recovery and retry logic - Dead letter queue handling

Monitor MCE consumer health:

# Check MCE consumer logs
kubectl logs -f <gms-pod> | grep "mce-consumer"

# Verify no backed up messages
# Check your Kafka topic lag

Fixed in version v0.3.11. If you continue to see MCE consumer errors after upgrading, check that your ingestion sources are emitting events in the correct format. The internal schema registry was also improved in v0.3.13 to better handle schema compatibility.

• Metadata Events
• Architecture Overview