How to deal with duplicated UUID files or anomalies in /var/lib/glusterd/peers

Solution In Progress - Updated -

Issue

  • A peer probe of a new node with a downed peer may cause a duplicated entry in peer status.
  • After a full recovery of a host, there is an anomaly in the config -
    the file name that contains the uuid of the host Gluster that is different from other servers of Gluster.
  • Some peers showing no volumes present and are missing from peer status
  • gluster volume status timeout after gluster server reboot

Environment

RHGS 3.1.*

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content