Bug 970183 - MapReduce Job submission should allow more than one user
MapReduce Job submission should allow more than one user
Status: VERIFIED
Product: GlusterFS
Classification: Community
Component: gluster-hadoop (Show other bugs)
mainline
Unspecified Unspecified
high Severity medium
: ---
: ---
Assigned To: Bradley Childs
Martin Bukatovic
: Triaged
: 968432 (view as bug list)
Depends On: 1061742
Blocks: 969195 969223 1056652 1057253
  Show dependency treegraph
 
Reported: 2013-06-03 11:51 EDT by Steve Watt
Modified: 2018-01-30 19:39 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1056652 (view as bug list)
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Steve Watt 2013-06-03 11:51:19 EDT
At present, for a MapReduce Job Submission to work, the user ID submitting the job should be the same user ID that started the JobTracker and TaskTracker. We need to be able to support Job Submission by multiple users as the current user (mapred) will not always have permissions to access all the data for all foreseeable Hadoop jobs.
Comment 2 Jay Vyas 2013-11-19 07:59:28 EST
Multitenancy has now been addressed, with an upcoming ACL patch to be released 
shortly.  

The solution is to add a hook into the file system which, and based on a regex, 
add ACL privileges for a hadoop / mapred daemon, so that it can always see any 
files which are jobtracker related.  This way, any user can submit a job and be 
gauranteed that the jobtracker daemon (specified in a config parameter), will 
be able to run that job. 

See https://forge.gluster.org/hadoop/pages/Security
Comment 3 Scott Haines 2013-11-19 14:37:25 EST
Per 11/13 bug triage meeting, re-assigning to bchilds.  Also marking MODIFIED.
Comment 4 Jay Vyas 2013-11-25 09:58:32 EST
*** Bug 968432 has been marked as a duplicate of this bug. ***

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