About Shelton

Shelton · ‎06-02-2017

@Karan Alang I think there is no better answer than this page I was jsut rading it some hours ago in the train it will just do exactly that ! kafka not in ISR

Shelton · ‎06-02-2017

@Joshua Adeleke HDP 2.6 uses the innoDB engine instead of MyISAM engine in comparison to earlier versions of HDP till 2.5.3 if you are running Mysql. You will need to change the execution engine to InnoDB so run the below statements to check all the tables while logged on as mysql root user you will need Converting an Existing Table SELECT`ENGINE`FROM`information_schema`.`TABLES`WHERE`TABLE_SCHEMA`='your_database_name'AND`TABLE_NAME`='your_table_name'; check table engine SHOW TABLE STATUS WHERE Name = 'xxx' Change the execution engine ALTER TABLE my_table ENGINE = InnoDB; Then you can restart your database and the errors shouldn't show. Hope that helps

Shelton · ‎05-31-2017

@priyanshu hasija Try the below steps $ klist -kt /etc/security/keytabs/hbase.service.keytab Keytab name: FILE:/etc/security/keytabs/hbase.service.keytab KVNO Timestamp Principal ---- ----------------- -------------------------------------------------------- 1 02/02/17 23:00:12 hbase/FQDN@EXAMPLE.COM 1 02/02/17 23:00:12 hbase/FQDN@EXAMPLE.COM 1 02/02/17 23:00:12 hbase/FQDN@EXAMPLE.COM 1 02/02/17 23:00:12 hbase/FQDN@EXAMPLE.COM 1 02/02/17 23:00:12 hbase/FQDN@EXAMPLE.COM Then from the above do this $ kinit -kt /etc/security/keytabs/hbase.service.keytab hbase/FQDN@EXAMPLE.COM Now run your job and let me know

Shelton · ‎05-23-2017

@Qinglin Xia What is the version of Atlas and HDP ?? I encountered the same issue on 2.5.0.0 but see this output with 2.5.3 on how to reproduce lineage. Make sure that the Ranger Plugins for Atlas ,hbase,hive,hdfs,kafka have been enable with corresponding Ranger Policies !! see the Additional Requirements for Atlas with Ranger and Kerberos Have a look at the attached document running Atlas in a kerberized the only difference if your environment is not kerberiszed s not to run the kinit:-)

Shelton · ‎05-22-2017

@priyanshu hasija, I assume you are on linux Check the valid principal for the hdfs keytab [root@toronto ~]# klist -kt /etc/security/keytabs/hdfs.headless.keytab Keytab name: FILE:/etc/security/keytabs/hdfs.headless.keytab KVNO Timestamp Principal ---- ----------------- -------------------------------------------------------- 1 05/08/17 23:33:51 hdfs-has@HASIJA.COM 1 05/08/17 23:33:51 hdfs-has@HASIJA.COM 1 05/08/17 23:33:51 hdfs-has@HASIJA.COM 1 05/08/17 23:33:51 hdfs-has@HASIJA.COM 1 05/08/17 23:33:51 hdfs-has@HASIJA.COM Kinit using the hdfs keytab and principal [root@toronto ~]# kinit -kt /etc/security/keytabs/hdfs.headless.keytab hdfs-has@HASIJA.COM Local file system [root@toronto ~]# ls anaconda-ks.cfg authorized_keys install.log install.log.syslog Now copy to hdfs [root@toronto ~]# hdfs dfs -copyFromLocal authorized_keys /user/admin Check the copy was successful [root@toronto ~]# hdfs dfs -ls /user/admin Found 1 items -rw-r--r-- 3 hdfs hdfs 405 2017-05-22 20:41 /user/admin/authorized_keys There you go

Shelton · ‎05-18-2017

@btandel Have a look at this

Shelton · ‎05-16-2017

@Debra Montague Make sure the encryption types are the same , also check that the KVNO (key version number) is the same ! See the syntax here Link

Shelton · ‎05-11-2017

@subash sharma Did you succeed with the hive metadata import in Atlas?

Shelton · ‎04-26-2017

Hi all, My problem has been resolved ! I had to ask the client to install a AD Explorer and figured out the correct settings and not only changed the baseDn all the group and user attributes ! authentication.ldap.baseDn=DC=hq,DC=uk,DC=com authentication.ldap.bindAnonymously=false authentication.ldap.dnAttribute=organizationalPerson authentication.ldap.groupMembershipAttr=member authentication.ldap.groupNamingAttr=cn authentication.ldap.groupObjectClass=group authentication.ldap.managerDn=cn=svc-hadoop-ldap,ou=Data Lake,ou=Applications,ou=Administrative,dc=hq,dc=uk,dc=com authentication.ldap.managerPassword=/etc/ambari-server/conf/ldap-password.dat authentication.ldap.primaryUrl=fake.uk.com:389 authentication.ldap.referral=ignore authentication.ldap.useSSL=false authentication.ldap.userObjectClass=organizationalPerson authentication.ldap.usernameAttribute=sAMAccountName This pulled out the desired users and group ambari-server sync-ldap --groups groups.txt Using python /usr/bin/python Syncing with LDAP... Enter Ambari Admin login: admin Enter Ambari Admin password:Syncing specified users and groups....Completed LDAP Sync.Summary: memberships: removed = 0 created = 4 users: updated = 0 removed = 0 created = 1 groups: updated = 0 removed = 0 created = 1

Shelton · ‎04-24-2017

@Vipin Rathor Sorry to get back this late I have just had acess again and I have change my baseDn to "DC=hq,DC=uk,DC=com" but that doesn't still pull the desired group. This is making me mad

Online	Offline
Last Visited	‎12-11-2025 11:50 PM

Member Since	‎01-19-2017 04:35 AM
Last Visited	‎12-11-2025 11:50 PM
Posts	3,679
Kudos received	627

Cloudera Community

Re: Apache nifi memory consumption in kubernetes

Re: Nifi toolkit command for GitLabFlowRegistry

Re: Not able to delete the NiFi existing flow usin...

Re: Securing Nifi with SSL and using OIDC provider...

Re: External zookeeper and nifi cluster connection...

Re: Kafka - simulating Brokers not being in sync (...

Re: DB Inconsistency Issues with HDP 2.6

Re: Unable to connect to kerberos hbase

Re: Atlas: How to generate lineage between hive ex...

Re: I have just setup kerberos witn hadoop. unable...

Re: Single Datanode start fails ?

Re: Kerberized Clusters - Can you have multiple ke...

Re: How to import hive metadata in Apache Atlas ??

Re: Sync ldap problem

Re: Sync ldap problem