NDS has timestamps on every transaction, every object, every attribute. This is to make sure the last change is effective: if we both reset a user's password, the change with the latest timestamp is kept. For this it is imperative that all servershave a synchronised time. Not much extraordinary there.
If you change the time on the server, from 10:00 to 09:00, then you risk having incorrect timestamps, and wrong interpretation of "the latest change". Therefor your servers will use "synthetic time" for NDS (and only for NDS!). NDS will use a slightly slower clock (in the case of my example), until "NDS time" is equal to "server time". This may take several hours or even days, depending on the change you made. If you reverse the timeby several days, you may even see this message for weeks to come.
In itself Synthetic Time is not a problem, on the contrary: it is a proof that your NDS is aware of a change, and is reacting correctly to it. However, if the Synthetic Time goes on for more than a day or so, it is better to get rid of it. You do this in:
-load dsrepair -a
-Advanced Options
-Replica and Partition operations
-
-Repair Time Stamps and declare a new epoch
This will, simply put, tell NDS to "start all over" from now, using the time of now. It may take a few minutes before the Synthetic messages disappear, but that is due to NDS synchronisation.
Jim