The mariadb-binlog client tool when used with the --flashback option, which reverts the transactions contained in the binary log, leaves the state of the server as it previous was (i.e. gtid_slave_pos, gtid_binlog_pos, etc).

Resetting the slave variables would be simple (e.g. mariadb-binlog could reset them to their earlier versions), but this would create inconsistency with the primary-side variables, which cannot be easily reset.

So a method to reset the state of the server in a consistent way should be implemented.