You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had an error in the schema and a client was not able to read the schema from the registry. In this case in the AbstractKafkaAvroSerializer in line 141 has catched the exception and created an errormessage. Then in line 176 the whole schema is added to the error message.
This was written as one message in the logs, but we cut messages with more than 16k chars. In json format this message got an invalid format and was not recognized from Kibana. After thousands of repeats the space in disk was running full.
Please reduce the amount of logdata. The ID and the name of the schema would be sufficient in this case.
Thanks Olli
The text was updated successfully, but these errors were encountered:
We had an error in the schema and a client was not able to read the schema from the registry. In this case in the AbstractKafkaAvroSerializer in line 141 has catched the exception and created an errormessage. Then in line 176 the whole schema is added to the error message.
This was written as one message in the logs, but we cut messages with more than 16k chars. In json format this message got an invalid format and was not recognized from Kibana. After thousands of repeats the space in disk was running full.
Please reduce the amount of logdata. The ID and the name of the schema would be sufficient in this case.
Thanks Olli
The text was updated successfully, but these errors were encountered: