Member since
11-15-2016
10
Posts
0
Kudos Received
0
Solutions
12-25-2017
12:00 PM
Clear the archives from log_archive_dest location Once you have make some space at the OS level then connect to the Oracle database as sysdba and execute below statements sqlplus / as sysdba archive log list; alter system switch logfile;
... View more
10-20-2017
09:45 PM
1 Kudo
Hi @sbx hadoop you should probably check with your local Hortonworks team for a proper answer. I don't think you need to worry about logically/physically moving anything, just ensuring that you have the proper support subscriptions in place from the HDP and HDF products that you need. Again, your local Hortonworks team can provide an official answer to your inquiry.
... View more
06-23-2017
07:14 AM
Hello @sbx hadoop , could you please proved additional info about how you configured your Kafka brokers ? Are there listeners for PLAINTEXT and/or SASL_PLAINTEXT , and which one relates to which port...since you used in your example 6667 and 9092 If e.g. port 9092 is configured for kerberized access, you also have to provide a proper JAAS config for starting the kafka-console-consumer (in addition to add parameter "--security-protocol" ). Assuming your user already has a valid kerberos ticket you can use that for auth => /tmp/test-jaas.conf: KafkaClient {
com.sun.security.auth.module.Krb5LoginModule required useTicketCache=true;}; This JAAS file needs to be added to your env. by exporting it, that the consumer can use it later on, e.g.: export KAFKA_KERBEROS_PARAMS=-Djava.security.auth.login.config=/tmp/test_jaas.conf
I am not sure if it is just a typo here, but you do not need to specify the same broker/zookeeper 3 times, this is useless 😉 (see e.g. --zookeeper property, the exact same value is specified 3 times...) HTH, Gerd
... View more
03-22-2017
10:19 PM
10 Kudos
Hi @sbx hadoop, Ranger provides an excellent auditing functionality that can be accessed easily through Ranger UI. After logging into ranger UI, click on Audit link from top global menu and then click on access tab. The resource access related logs are found here. Pls note the access logs will be generated only if the Ranger plugin for that component is enabled and working fine. This page shows you the following: Date and time at which the resource access was attempted, user which tried to access the resource, service to which the resource belongs and whose policies come into play, Resource name and type (Ex: type = column-family if the operation was related to hbase col family ), Access Type [Eg: get for hbase], Result - Allowed/ Denied, Access Enforcer=ranger-acl/ hadoop-acl, and the policy which granted access. In case of Access Enforcer=ranger-acl and result=denied, the policy-id field will show a '--' which means that the user didn't have any Ranger policy for that resource and so the access was denied. In case of Access Enforcer=ranger-acl and result=allowed, the policy-id field will show the policy-id link, which means that the user had access to the resource through that particular policy. Clicking on the link will show you the policy details. Also the search feature helps you in streamlining your search by entering various search inputs. Hope this helps.
... View more