On 9 September 2017 at 05:17, Ravi Prakash wrote:
> I'm not sure my reply will be entirely helpful, but here goes.
It sheds more light on things than I previously understood, Ravi, so cheers
> The ResourceManager either proxies your request to the ApplicationMaster (if
>
Hi again,
my attempts to Kerberise our Hadoop instance seem to
have things working OK, although one of the users has
reported the following issue:
The console output, from a running job, suggests following a link to
the RM server's WebGUI, akin to
Hi again
early on in my attempts to Kerberise our Hadoop instance, I had seen an
error message that suggested I needed to add a list of users who could
run jobs into the last line of Hadoop's
container-executor.cfg
for which the default content is
On 25 July 2017 at 03:21, Erik Krogen wrote:
> Hey Kevin,
>
> Sorry, I missed your point about using auth_to_local. You're right that you
> should be able to use that for what you're trying to achieve. I think it's
> just that your rule is wrong; I believe it should be:
>
On 21 July 2017 at 13:25, Kevin Buckley
<kevin.buckley.ecs.vuw.ac...@gmail.com> wrote:
> On 21 July 2017 at 04:04, Erik Krogen <ekro...@linkedin.com> wrote:
>> Hi Kevin,
>>
>> Since you are using the "jhs" keytab with principal "jhs/_h...@realm.tld&
On 21 July 2017 at 04:04, Erik Krogen wrote:
> Hi Kevin,
>
> Since you are using the "jhs" keytab with principal "jhs/_h...@realm.tld",
> the JHS is authenticating itself as the jhs user (which is the actual
> important part, rather than the user the process is running as).
I've noted in
https://hadoop.apache.org/docs/r2.8.0/hadoop-project-dist/hadoop-common/ClusterSetup.html
that it says
8<8<8<8<8<
See etc/hadoop/hadoop-env.sh for other examples.
Other useful configuration parameters that you can customize