Ideally a same node shouldn't have multiple UUIDs, which is unfortunately
true in your setup. I do not see any straight forward case which can lead
to this issue. What Gluster version are you using?
-Atin
Sent from one plus one
On Sep 19, 2015 4:40 AM, "John Casu" wrote:
> Hi,
>
> we're seeing m
also, gluster volume status takes *forever* to run, & returns no useful info
On 9/18/15 4:10 PM, John Casu wrote:
Hi,
we're seeing multiple entries for nodes in pool list & peer status, each
associated with a unique UUID.
Filesystem seems to be working, but we need to clean this up in anticip
Hi,
we're seeing multiple entries for nodes in pool list & peer status, each
associated with a unique UUID.
Filesystem seems to be working, but we need to clean this up in anticipation of
any future issues.
The nodes with multiple UUIDs were previously disconnected, but they're good
now.
Doe
