Description of problem:
An issue came up where my log files over ran my /var partition, this caused my volume configurations to become corrupt on several servers. Because the of the issue I needed to copy the config files from a known good host using the gluster commands to do so. 

Part of the resolution was to re-probe the servers to get them back in sync. I ended up with several servers who's UUID's did not match the peer files across the cluster. The gluster commands would work intermittently if I spammed the commands and the cluster and volume was functioning, but not optimally, it would suffer a lot of what seemed to be random disconnects, etc. 

What I was seeing was that the glusterd.info file on server1 would have a UUID of 6e5df7ab-4440-49b2-9aa7-a5984391b5f5, but it's peer files on each of the other 10 servers would either reference the correct 6e5df7ab-4440-49b2-9aa7-a5984391b5f5 or 35e62be3-752e-48aa-aa15-dc68abfaf06f (these UUID's are only examples). 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

The system ran in an inconsistent state even though the UUID's configurations didn't match across the cluster. 


Expected results:

The system would not function until the UUID's were corrected. 


Additional info:

It might be useful to have some sort of UUID consistency check algorithm that either stops the system and throws an error, or is intelligent enough to correct the problem.