Bug 1425389

Summary:	GlusterFS and daily reboot and Java Hibernate Search produce problems
Product:	[Community] GlusterFS	Reporter:	Peter Dyballa <Peter_Dyballa>
Component:	fuse	Assignee:	Raghavendra G <rgowdapp>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.8	CC:	bugs
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-07 10:42:24 UTC	Type:	Bug
Regression:	---	Mount Type:	fuse
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Dyballa 2017-02-21 10:26:15 UTC

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

Comment 1 Kaushal 2017-03-08 10:51:41 UTC

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.

Comment 2 Peter Dyballa 2017-03-10 09:02:52 UTC

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…

Comment 3 Peter Dyballa 2017-03-23 08:51:59 UTC

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)

Comment 4 Niels de Vos 2017-11-07 10:42:24 UTC

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.