Bug 797160

Summary:	mountpoint needs to be unmounted when stop-mapred is issued.
Product:	[Community] GlusterFS	Reporter:	M S Vishwanath Bhat <vbhat>
Component:	HDFS	Assignee:	Steve Watt <swatt>
Status:	CLOSED EOL	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	pre-release	CC:	bugs, gluster-bugs, mzywusko
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-22 15:40:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description M S Vishwanath Bhat 2012-02-24 12:28:22 UTC

Description of problem:
glusterfs-hadoop plugin mounts the gluster volume created in both master and slaves when any fs or jar operations are run. But when ./bin/stop-mapred.sh is issued these mountpoint needs to be unmounted. 

Version-Release number of selected component (if applicable):
master

How reproducible:
always

Steps to Reproduce:
1. Run ./bin/start-mapred.sh from $HADOOP_HOME
2. Run any fs operations like ./bin/hadoop fs -ls / . This actually mounts gluster volume in master and all slaves.
3. Run ./bin/stop-mapred.sh
  
Actual results:
mounted gluster volume is still mounted in all the machines of the cluster.

Expected results:
When ./bin/stop-mapred.sh is issued, all these mountpoints needs to be unmounted.

Comment 1 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC

pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.