Description of problem: We have two servers that share data via GlusterFS. Since they reside in integration and are located in the Amazon cloud (AWS/EC2) they are stopped in the evening and started next morning. This situation seems to produce errors. The main application that uses the shared data is Java based (1.8.0_112) and uses Tomcat (8.5.11). The Java applications won't launch when Hibernate Search is not working. It also shares data (index files) in the cluster, and particularly here, in /next-shared which is accessed via a stable and reliable sym-link because of so many changes in layout, is the source of all trouble. The file systems are: Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/vg00-gluster ext4 2.0G 285M 1.6G 16% /gluster /dev/mapper/vg00-srv ext4 4.8G 2.4G 2.2G 53% /srv /var/lib/glusterd/vols/next-shared/next-shared-fuse.vol fuse.glusterfs 2.0G 285M 1.6G 16% /next-shared Version-Release number of selected component (if applicable): 3.7.20 in integration (3.5.9 in production without steady reboots) How reproducible: stop/start server daily, presumingly Steps to Reproduce: 1. 2. 3. Actual results: Index files faulty that Java Hibernate Search won't launch so that Tomcat using Java applications won't work Expected results: Working as in production (three servers in GlusterFS cluster running all the time, except for occasional reboots after OS updates) Additional info: Ubuntu 14.04.5 LTS, not really used (beginner) to GlusterFS
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.
I upgrade to ii glusterfs-client 3.8.9-ubuntu1~trusty1 amd64 clustered file-system (client package) ii glusterfs-common 3.8.9-ubuntu1~trusty1 amd64 GlusterFS common libraries and translator modules ii glusterfs-server 3.8.9-ubuntu1~trusty1 amd64 clustered file-system (server package) and the problem still persists…
The problem persists with ii glusterfs-client 3.8.10-ubuntu1~trusty1 amd64 clustered file-system (client package) ii glusterfs-common 3.8.10-ubuntu1~trusty1 amd64 GlusterFS common libraries and translator modules ii glusterfs-server 3.8.10-ubuntu1~trusty1 amd64 clustered file-system (server package)
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.