Bug 797160 - mountpoint needs to be unmounted when stop-mapred is issued.
Summary: mountpoint needs to be unmounted when stop-mapred is issued.
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: HDFS
Version: pre-release
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: Steve Watt
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-24 12:28 UTC by M S Vishwanath Bhat
Modified: 2016-06-01 01:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-10-22 15:40:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


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