Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Does using Custom Service names (e.g. hdfs_prod) and DB user names (e.g. hive_db_user) instead of the defaults, create potential issues during future upgrades ?

Solved Go to solution
Highlighted

Does using Custom Service names (e.g. hdfs_prod) and DB user names (e.g. hive_db_user) instead of the defaults, create potential issues during future upgrades ?

Custom Service names are supported in HDP. So this might be a moot question. Just want to see if anyone has experience with this issue :

does using Custom Service names (e.g. hdfs_prod) and DB user names (e.g. hive_db_user) instead of the defaults, create potential issues during future upgrades ?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Does using Custom Service names (e.g. hdfs_prod) and DB user names (e.g. hive_db_user) instead of the defaults, create potential issues during future upgrades ?

Do you use Ambari? If so, then there should be no problems as the service user information is recorded in Ambari and propagates through with upgrades. If you don't, then you probably just have to make sure you copy across any relevant configuration parameters, remember to start your services as that user and check HDFS permissions are correct as part of the post-upgrade validation process.

As you say, custom users are totally supported, so you shouldn't experience any problems.

View solution in original post

1 REPLY 1

Re: Does using Custom Service names (e.g. hdfs_prod) and DB user names (e.g. hive_db_user) instead of the defaults, create potential issues during future upgrades ?

Do you use Ambari? If so, then there should be no problems as the service user information is recorded in Ambari and propagates through with upgrades. If you don't, then you probably just have to make sure you copy across any relevant configuration parameters, remember to start your services as that user and check HDFS permissions are correct as part of the post-upgrade validation process.

As you say, custom users are totally supported, so you shouldn't experience any problems.

View solution in original post

Don't have an account?
Coming from Hortonworks? Activate your account here