Member since
09-11-2017
5
Posts
2
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
7034 | 04-19-2018 08:55 AM |
04-19-2018
08:55 AM
2 Kudos
I had to reset the Navigator metadata server and followed the steps below: 1) Stop Navigator Metadata Server from CM 2) Take a back up of Navigator Metadata Server Storage Dir (if you want to archive the old data) 3) mv <storage_dir> < new_location> 4) Back up your navms database 5) In NMS database run: "DELETE FROM NAV_UPGRADE_ORDINAL;" "INSERT INTO NAV_UPGRADE_ORDINAL VALUES (-1, -1);" 6) Start Navigator Metadata Server this will delete all metadata, custom data added in the Navigator UI but does not affect the Audit logs visible under Navigator UI -> Audits.
... View more
02-09-2018
05:39 AM
Hi @mlussana1, I have configured Kafka(2.2.0) with Sentry enabled in Kerberized environment and be able to use it as channel for Flume in CDH 5.13. First of all did you add the kafka to the Allowed Connecting Users(sentry.service.allow.connect) in sentry configuration?And in order to give privilege your user must be in one of the sentry admin groups which are listed in Admin Groups(sentry.service.admin.group) configuration.Those may cause the sentry shell problem. For the producer problem ,I am not sure but you may modify the jass.conf file as follows: KafkaClient { com.sun.security.auth.module.Krb5LoginModule required useKeyTab=false useTicketCache=true serviceName="kafka" principal="username@xxxx.xxx"; }; Client { com.sun.security.auth.module.Krb5LoginModule required useKeyTab=false useTicketCache=true serviceName="zookeeper" principal="username@xxxx.xxx"; }; And I run the consumer and producer from command line as follows: kafka-console-consumer --topic topicname --from-beginning --bootstrap-server brokerhostname:9092 --consumer.config consumer.properties kafka-console-producer --broker-list [brokers]:9092 --topic topicname --producer.config client.properties I hope these would help.
... View more
02-09-2018
04:41 AM
Hi @bgooley , (1)rpm -qa | grep cloudera gives the following output: cloudera-manager-agent-5.13.1-1.cm5131.p0.2.el7.x86_64 cloudera-manager-daemons-5.13.1-1.cm5131.p0.2.el7.x86_64 cloudera-manager-server-5.13.1-1.cm5131.p0.2.el7.x86_64 (2)And the query result is: ordinal | old_ordinal ---------+------------- 26 | 26 Thanks
... View more
01-30-2018
04:25 AM
Hi, can you find a solution for this issue? Thanks
... View more