Our mxs_adapter service runs on server cdc1 querying Maxscale on server maxscale1. On restart of the mxs_adapter service, maxscale takes ~2.5 mins to read the entire x.x.000001.avro file until it reaches the GTID position specified by mxs_adapter.
During this start up requests to maxscale fail with socket timout.
Once maxscale locates this position it seems to perform just fine.
Our .avro file is now 2.5GB in size after a day and half of processing data.
Is there a way to handle data pruning in the avro file? And is the some way to improve cdc request startups so that maxscale requests can be handled during the process?