Gluster health process crashes on replace-brick operation with Red Hat Gluster Server
Issue
- We are migrating production
glusterfs
cluster to a new cluster servers with a new ip range. From 20 replace brick commands, there were two core dumps of the health daemon on the target system. Below is a example of the command that was run:
gluster volume replace-brick vol_example01_pv1 10.1.1.19:/gluster/slow/example01/pv1/brick 10.20.21.178:/gluster/project/example01/pv1/brick commit force
Environment
- Red Hat Gluster Server 3.2 and 3.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.