If Karapace would expect to consume multiple records after startup, there is extra latency of the consumption timeout as consumer does not return control back to schema reader until it happens. This would cause extra latency when storing schema.
On normal operating mode after startup there expectation is to process single record at a time and return control immediately to schema reader when record is available.
About this change - What it does
If Karapace would expect to consume multiple records after startup, there is extra latency of the consumption timeout as consumer does not return control back to schema reader until it happens. This would cause extra latency when storing schema. On normal operating mode after startup there expectation is to process single record at a time and return control immediately to schema reader when record is available.