Member since
01-19-2017
3682
Posts
633
Kudos Received
373
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1734 | 06-04-2025 11:36 PM | |
| 2166 | 03-23-2025 05:23 AM | |
| 1035 | 03-17-2025 10:18 AM | |
| 3967 | 03-05-2025 01:34 PM | |
| 2710 | 03-03-2025 01:09 PM |
04-23-2019
12:28 PM
@Dennis Suhari If you found this answer addressed your question, please take a moment to log in and click the "accept" link on the answer. That would be a great help to Community users to find the solution quickly for these kinds of errors.
... View more
04-23-2019
05:21 AM
1 Kudo
@Michael Bronson Out of the box configs are much easier but the config you have implemented is the correct way to integrate Presto with hadoop these files must be present on all the presto node 🙂
... View more
04-23-2019
04:12 AM
@Shilpa Gokul Please have a look at this HCC document by Neeraj Sabharwal how to setup kafka/ranger without Kerberos This should still be valid with a few tweaks
... View more
04-22-2019
03:55 PM
@Shilpa Gokul Is the plugin enabled for kafka?
... View more
04-21-2019
09:44 AM
@Shilpa Gokul There is information that you should have provided to help members help you resolve your problem. Is you cluster kerberized? What is the command you are executing? Can you share your Ranger/ kafka policy configuration?
... View more
04-18-2019
10:44 AM
1 Kudo
@Afroz Baig Firstly you really don't need to modify manually the krb5.conf as they MUST be identical on all the cluster nodes. What you should do is run scp from the Ambari server where you configured the passwordless connection. Assuming your Ambari Server hosts file entry has all the cluster node and egdenode1 is your target # scp /etc/krb5.conf root@edgnode1:/etc/ This will copy and overwrite the incorrect krb5.conf on the edge node. Assuming you have a user named analyst01 on the edge node who intends to run a job after the update you will do the following as user analyst1 assuming he has his keytab in his home directory # su - analyst01 To determine if he has a valid ticket, in the below he didn't have one # klist klist: No credentials cache found (filename: /tmp/krb5cc_0) Grab a ticket $ kinit -kt /home/analyst01/analyst01.keytab Now he should be able to grab a valid ticket and the klist should validate that $ klist
Ticket cache: FILE:/tmp/krb5cc_1013
Default principal: analyst01-xxx@{REALM}
Valid starting Expires Service principal
04/13/2019 23:25:32 04/14/2019 23:25:32 krbtgt/_host@{REALM}
04/13/2019 23:25:32 04/14/2019 23:25:32 HTTP/_host@{REALM} You don't need to restart any services on the edge node !
... View more
04-17-2019
10:40 AM
@Dennis Suhari The command you are running is wrong , it's the wrong variation you forgot a dash - Note the space before and after the dash !! As the root user run # su - yarn That should work HTH
... View more
04-16-2019
01:54 PM
@Naveenraj Devadoss Did you remember this part? "You'll also need to ensure that the machine where NiFi is running has network access to all of the machines in your Hadoop cluster." Please revert
... View more
04-16-2019
06:37 AM
@Naveenraj Devadoss You need to copy the core-site.xml and hdfs-site.xml from your HDP cluster to the machine where NiFi is running. Then configure PutHDFS so that the configuration resources are "/path/to/core-site.xml,/path/to/hdfs-site.xml". That is all that is required from the NiFi perspective, those files contain all of the information it needs to connect to the Hadoop cluster. You'll also need to ensure that the machine where NiFi is running has network access to all of the machines in your Hadoop cluster. You can look through those config files and find any hostnames and IP addresses and make sure they can be accessed from the machine where NiFi is running. HTH
... View more