[
https://issues.apache.org/jira/browse/MAPREDUCE-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-1376:
-------------------------------------
Attachment: M1376-2.patch
bq. Please open a jira to enhance rumen to extract UGI mapping information from
job traces.
Filed MAPREDUCE-1384
bq. There is no API documentation of the interface methods in UserResolver.
bq. Newly added conf parameters are not updated in GridMix.printUsage() method.
bq. There seems to be a typo in UserResolver javadoc "Maps users to a set of
users on the test cluster." => "Maps users to a set of groups on the test
cluster."
That wasn't a typo, but it's clearly not a helpful comment. Replaced with "Maps
users in the trace to a set of valid target users on the test cluster." Also
added interface and option documentation.
bq. The interface of UserResolver.setTargetUsers() requires the userspec to be
stored in a file. How about changing it to
"setTargetUsers(List<UserGroupInformation>, Configuration conf)"? [snip] This
would also require UserResolver.parseUserList moved to GridMix.run()
This was the first interface I tried, but a {{UserResolver}} is really just
getting an (optional) URI argument and a conf. How/whether it builds a user
list from that resource may be specific to the {{UserResolver}} implementation.
Since \-users is a command-line param, I gave it a {{Path}} type and assume
that will be sufficient. I left the parsing of the default file format in the
base class, so I agree that it's likely the only implementation, but I left it
as a member function so it's easy to override.
bq. Also currently EchoUserResolver/SubmitterUserResolver ignores this info,
maybe we can have the method to return a boolean to indicate whether the method
call takes effect or not?
The driver would probably ignore that feedback, wouldn't it?
bq. Any reason we split GridMix.run() to GridMix.run() and GridMix.start() now?
The command-line parsing was becoming less trivial, but breaking it into a
method called by run would have been uglier. Either way is fine w/ me; any
preference?
> Support for varied user submission in Gridmix
> ---------------------------------------------
>
> Key: MAPREDUCE-1376
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1376
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/gridmix
> Reporter: Chris Douglas
> Assignee: Chris Douglas
> Attachments: M1376-0.patch, M1376-1.patch, M1376-2.patch
>
>
> Gridmix currently submits all synthetic jobs as the client user. It should be
> possible to map users in the trace to a set of users appropriate for the
> target cluster.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
