I think the following may work:
- backup that node
- stop the aerospike service on the bad node (32 minutes ahead)
- stop the ntp service
- set the date
- shutdown the node
- power up the node
- adjust time again if data is still incorrect
- empty the aerospike data storage(s) and/or digestlog
- startup aerospike again
The remaining nodes should handle the normal traffic although there could be performance impact due to migration so monitor the cluster carefully.
If you don’t empty the storage, you may have the risk of resurrecting deleted data or losing updates due to generation wrap. See this for details: https://discuss.aerospike.com/t/conflict-resolution-policy-setting-usage/818
Adding an empty node will cause more traffic on the fabrics so again please monitor system carefully.
Hope that make sense and helpful.