The “moving_data.total_written_bytes” parameter is reset to 0 from time to time. At what time or under what conditions is it reset?
Below is a screenshot of the parameter over the last 4 days in our cluster. The reset was not fixed at specific time of the day. I was wondering a condition like “after no data movement for certain period”, but it doesn’t seem to work that way either.
Understanding the reset triggering conditions can help us better estimate impacts of specific FDB operations.