Context
It is possible for a cluster to hit stop writes due to clock_skew_stop_writes_sec getting breached. For AP mode this is 40s. For SC mode (strong consistency), this is 20s. Since clock_skew_stop_writes_sec is not configurable, you would need to verify that clocks are synchronized across the cluster to resolve this.
Method
The recommended method is to synchronize your clocks across the cluster. You can use tools such as ntp. For more details on how to set it up, please refer to our KB on How to configure ntp for Aerospike.