We had an issue where processes putting avro encoded messages onto the kafka topic were doing so with valid avro, but an invalid schema id. This should not happen, but it did happen. Anyway, this is what we did to get around it, by logging the message we can track down the process which created it, but not crash logstash (which is the current behavior).
We had an issue where processes putting avro encoded messages onto the kafka topic were doing so with valid avro, but an invalid schema id. This should not happen, but it did happen. Anyway, this is what we did to get around it, by logging the message we can track down the process which created it, but not crash logstash (which is the current behavior).