What is the behavior of MIN_ACTIVE_ROWVERSION() on replicas in SQL Server AlwaysOn? MIN_ACTIVE_ROWVERSION() returns the lowest rowversion allocated within still-open transactions. This is important when using rowversion columns for reading data where you want to be sure that you wont subsequently miss rows that have been written with rowversions lower than the batch you have just read.

What is the behaviour of this function when called on synchronous and asynchronous replicas in an AlwaysOn Availability Group situation?
On further investigation, it appears than MIN_ACTIVE_ROWVERSION() only behaves correctly on the primary instance, as that is the only place the full transactions are running on.