About stevenmatison

stevenmatison · ‎01-06-2020

Nice one!! Always restart Ambari after any Ambari-server setup commands. Very glad to see you got it!

stevenmatison · ‎01-04-2020

In working with some advanced features (enable/disable compatibility) I was able to find the Swagger API link for my Schema Registry. The link should look like: http://hdf.cloudera.com:7788/swagger/#/ Simply add /swagger/ after your Schema UI port and it will take you there.

stevenmatison · ‎01-04-2020

To change datatype or column names you need to use DISABLE as seen below:

stevenmatison · ‎01-03-2020

How many nodes are in your NiFi? How many cores per node? I see you have concurrency set to 90 and in the screen shot ~2400 active threads. At this point, your tuning is going to be at the Nifi cluster level (ram, cores, more nodes). You will also need to evaluate Garbage Collection on the NiFI nodes. Another thing to check out would be these admin settings: https://community.cloudera.com/t5/Community-Articles/Understanding-NiFi-max-thread-pools-and-processor-concurrent/ta-p/248920

stevenmatison · ‎01-03-2020

Looks like they did block public access to 2.7.5... the documentation indicates the info will be sent to your licensed support contact via email, or requested as below: Authentication credentials for new customers and partners are provided in an email sent from Cloudera to registered support contacts. Existing users can file a non-technical case within the support portal (https://my.cloudera.com) to obtain credentials.d If you want 2.7.5 without a support contract, you may want to go directly to the source: https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.5 Prior to this recent change, this is all you need to get the ambari and hdp repos: wget -O /etc/yum.repos.d/ambari.repo http://public-repo-1.hortonworks.com/ambari/centos7/2.x/updates/2.7.3.0/ambari.repo then yum install ambari-server ambari-agent -y The example above is for centos, other flavors should be similarly fetched and installed.

stevenmatison · ‎01-02-2020

My best advice is to copy from another known location. Either another node which was not effected by the delete, or a new node installed exactly same as node which had items deleted (incase these files might be specific to a node hostname or configuration). If the files are just common libraries, you should be able to copy from any known location just make sure you get the correct user/permissions after replacing the missing files. With great power comes great responsibility. Do not accidentally delete anything which is not backed up.

stevenmatison · ‎01-02-2020

Seems like you do not have the right settings. I would look into the CN value. You may be syncing the users at a DN higher level, and then the auth string is invalid because the CN value is wrong. Sorry I can't be more helpful, but as I suggest in my original post, going through the ambari ldap setup, will help identify what the correct strings are. It is usually a challenge even if someone says "here are all the settings".

stevenmatison · ‎01-02-2020

Are the FQDN hostnames properly setup and properly listed in /etc/hosts, before ssh-keygen? After you add SERVER A key to authorized_keys on SERVER B, do a ssh from Server A to B: ssh root@fqdn.serverb.com and you should get a prompt to accept the login (y/n), choose y and enter. Then test Install Agent. If the SERVER A to B root login step does not work , you do not have the keys correct in ~/.ssh/authorized_keys.

stevenmatison · ‎12-31-2019

The post says LDAP, and are you not trying to sync the LDAP users and groups to ranger? Wouldn't knowing what the required settings for each sync be helpful? Kerberos is another beast, which I personally would not complete until ambari and ranger integration is already completed.

stevenmatison · ‎12-31-2019

This may be slightly off topic, but when doing AD/LDAP Integration, I always start with the Ambari LDAP part first. This helps me identify the settings required to connect from Ambari -> LDAP, and the correct settings for user sync and group sync (sometimes different). While executing this command I also tail the log file for additional output that is required to debug the connection, and sync parts. After completing these steps, I then have clear idea of what settings can be used for Ranger. Helpful Links: https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.4/ambari-authentication-ldap-ad/content/authe_ldapad_configuring_ambari_for_ldap_or_active_directory_authentication.html https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.4/ambari-authentication-ldap-ad/content/authe_ldapad_synchronizing_ldap_users_and_groups.html

Online	Offline
Last Visited	‎06-01-2022 03:47 PM

Name	Steven Matison
Location	Florida
Member Since	‎07-19-2018 04:45 PM
Last Visited	‎06-01-2022 03:47 PM
Posts	613
Kudos received	101

Cloudera Community

Re: Apache nifi - how to convert a file .txt into ...

Re: Apache Nifi - Using PutParquet, the HDFS file ...

Re: How to extract csv column record and used it f...

Re: Could not connect to Distributed Map Cache ser...

Re: NiFi InvokeHTTP POST JSON

Re: hdfs groups not returning mapped groups using ...

Re: Using the Schema Registry API

Re: Change data type of a field in schema registry

Re: Nifi splitJson is becoming bottleneck

Re: Accessing Ambari Repositories

Re: Recover deleted folders from Cloudera cluster ...

Re: hdfs groups not returning mapped groups using ...

Re: Exhausted available authentication methods dur...

Re: hdfs groups not returning mapped groups using ...

Re: hdfs groups not returning mapped groups using ...