MaxScale does not have time to open the file during rotation for a new binlog

MaxScale works in binlogrouter mode.
Router = binlogrouter, Params in attach Params.json
binlog_size=1G
When rotating binlogs, maxscale does not have time to create a new file and make it writable. In this case, an error occurs when recording a portion of transactions (maxscale.log). It may be necessary to create the next binlog file in advance and keep it open. Don't wait until the current binlog file ends, but always have +1 for the next binlog file.
At the same time, the slave mariadb cannot receive transactions that remained in the write buffer (for old closed binlog file) and were written to a new binlog file (mariadb_slave.log).
Examples of searching for two transactions from the last two errors in the maria_slave.log file
(last2errors.log)