[
https://issues.apache.org/jira/browse/MAPREDUCE-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-1376:
-------------------------------------
Attachment: M1376-3.patch
bq. The added set of publicly visible configuration parameters, such as
GRIDMIX_USR_RSV, are still not documented in printUsage() method.
Sorry; I'd included this change, but must not have regenerated the patch.
bq. I'd suggest we decouple the logic of obtaining the list of target users
from resolving source users to target users.
I agree that the strategy for obtaining the list of users is a reasonable
abstraction, but why would this be part of the driver and not the user
resolution types? I've changed the {{Path}} type to a {{URI}} to be more
general, but emphasize that it's only there for usability. Any of the
alternative specs you propose- including the command-line- can be implemented
using Configuration and GenericOptionsParser.
It seems most of our disagreement would go away if I just removed the \-users
parameter and all resolution was done through Configuration.
bq. There could be a couple of possible enhancements based such feedback: One
is to issue an INFO/WARN log by Gridmix3 in the case when the resolver ignores
the targeted user list. [...]
Whether the resource is used is implicit in the contract of the particular
{{UserResolver}} isn't it? I added the warning, anyway.
----
It's worth pointing out that (the now PA) HADOOP-6299 completely invalidates
this patch. Many of the classes will no longer exist after its imminent commit.
> 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,
> M1376-3.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.
