Chapter 3. Known Issues
This chapter provides a list of known issues at the time of release.
- In a gluster cluster with more than three nodes, if one or more nodes are down, but at least three nodes are up, heketi intermittently fails to create new replica 3 volumes, even if the healthy nodes have sufficient space available.To workaround this issue, execute the following commend on the unavailable nodes, which makes heketi volume creation 100% reliable:
heketi-cli node disable <node-id>
# heketi-cli node disable <node-id>Copy to Clipboard Copied! Toggle word wrap Toggle overflow After the nodes are available again, execute the following command to let heketi take this node into account again when creating volumes:heketi-cli node enable <node-id>
heketi-cli node enable <node-id>Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Volumes that were created using Container-Native Storage 3.5 or previous do not have the GID stored in heketi database. Hence, when a volume expansion is performed, new bricks do not get the group ID set on them which might lead to I/O errors.
- The following two lines might be repeatedly logged in the rhgs-server-docker container/gluster container logs.
[MSGID: 106006] [glusterd-svc-mgmt.c:323:glusterd_svc_common_rpc_notify] 0-management: nfs has disconnected from glusterd. [socket.c:701:__socket_rwv] 0-nfs: readv on /var/run/gluster/1ab7d02f7e575c09b793c68ec2a478a5.socket failed (Invalid argument)
[MSGID: 106006] [glusterd-svc-mgmt.c:323:glusterd_svc_common_rpc_notify] 0-management: nfs has disconnected from glusterd. [socket.c:701:__socket_rwv] 0-nfs: readv on /var/run/gluster/1ab7d02f7e575c09b793c68ec2a478a5.socket failed (Invalid argument)Copy to Clipboard Copied! Toggle word wrap Toggle overflow These logs are added as glusterd is unable to start the NFS service. There is no functional impact as NFS export is not supported in Containerized Red Hat Gluster Storage.