Bug 797160 - mountpoint needs to be unmounted when stop-mapred is issued.
mountpoint needs to be unmounted when stop-mapred is issued.
Status: CLOSED EOL
Product: GlusterFS
Classification: Community
Component: HDFS (Show other bugs)
pre-release
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Steve Watt
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-24 07:28 EST by M S Vishwanath Bhat
Modified: 2015-10-22 11:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-22 11:40:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description M S Vishwanath Bhat 2012-02-24 07:28:22 EST
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 11:40:20 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.