Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hardcoded hdfs user doesn't work in clusters with personalized usernames #31

Open
chusopr opened this issue Sep 5, 2016 · 0 comments
Open

Comments

@chusopr
Copy link

chusopr commented Sep 5, 2016

Install script runs some commands as hardcoded hdfs user:

Execute('hadoop fs -mkdir -p /user/' + user, user='hdfs', ignore_failures=True) 
Execute('hadoop fs -chown ' + user + ' /user/' + user, user='hdfs') 
Execute('hadoop fs -chgrp ' + user + ' /user/' + user, user='hdfs') 

Execute('hadoop fs -mkdir -p ' + spark_jar_dir, user='hdfs', ignore_failures=True) 
Execute('hadoop fs -chown ' + user + ' ' + spark_jar_dir, user='hdfs') 
Execute('hadoop fs -chgrp ' + user + ' ' + spark_jar_dir, user='hdfs') 

This won't work if the cluster uses a diferent user (in our organization we prefix the username with the cluster name: <clustername>-hdfs:

Skipping failure of Execute['hadoop fs -mkdir -p /user/zeppelin'] due to ignore_failures. Failure reason: Execution of 'hadoop fs -mkdir -p /user/zeppelin' returned 1. 16/09/05 15:15:47 WARN ipc.Client: Exception encountered while connecting to the server : 
javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant