Mariadb with more than one node each node will have recent 1 year data
You may want to look at the MariaDB Spider storage engine which is a sharding engine that allows you to partition the data e.g. by range so that data in a certain range will be stored on a certain backend server.

Let's say you have a table with year column. You can then say that values in a particular year should go to a particular backend server. See some example use cases here.

This will give you node 1 for the first year, node 2 for the second year and so on, and no shifting of data, but that is probably better anyway. You can always rename the servers, if that helps. 

If you're storing a new row every second, that means 31,536,000 rows per year, which is probably absolutely fine, though it's always a good idea to make sure the table(s) are optimally designed especially when you're storing a lot of data like this.