Gluster users - Dec 2013 - node with out of sync clock

All:

We had a node in one of our gluster instances where the clock was behind 
by ~ 100 s from the other three nodes.
Eventually, we had an incident on that particular node, and we had two 
of the KVM VMs it hosts go read-only (their local filesystems were 
mounted error=continue).

Could this have been caused by the out of sync clock?

Thanks.