About tusharkathpal

tusharkathpal · ‎06-16-2021

Hello @pauljoshiva If the crashed data node comes up, then the data replica count will be 4 that is the case of over replicated blocks.HDFS will automatically delete the excess replicas as the default replication factor has to be maintained 3. The replica from the now active datanode is going to be removed. https://docs.cloudera.com/runtime/7.2.9/hdfs-overview/topics/hdfs-how-namenode-manages-blocks-on-a-failed-datanode.html

tusharkathpal · ‎05-20-2021

It seems a wrong configuration/password is passed in ranger configuration which is unable to open the keystore using the same. $JAVA_HOME/keytool -list -keystore <keystore path with .keystore.jks> -storepass <password> Check with the above command if you are able to list the keystore contents using the password you pass above. Ensure the same is configured in the ranger configuration.

tusharkathpal · ‎05-20-2021

@dmharshit A znode is supposed to be formed under zookeeper. Check for zookeeper logs during the HS2 start as to why it is or HS2 is not able to create znode.

tusharkathpal · ‎05-03-2021

In Beeline, the command-line options such as sslTrustStore, trustStorePassword, showDbInPromp etc are case sensitive. For example, below is a working connection string from a test bed: beeline -u "jdbc:hive2://host-A-fqdn:21051/default;principal=impala/host-A-fqdn@COE.CLOUDERA.COM;ssl=true;sslTrustStore=/opt/cloudera/security/truststore.jks" In the above example, the common mistakes are principal mentioned as Principal and sslTrustStore mentioned as ssltruststore. Here, if the case sensitivity is not followed, Beeline silently ignores the command line options and drops them: //Sample string beeline -u "jdbc:hive2://host-A-fqdn:21051/default;Principal=impala/host-A-fqdn@COE.CLOUDERA.COM;ssl=true;ssltruststore=/opt/cloudera/security/truststore.jks" If you use the above connection string, at first, you will encounter a Kerberos issue as the property "principal" will be dropped and the actual Kerberos authentication will fail. If you fix the Kerberos issue, then you would encounter SSL related error as the ssltruststore needs to be written as "sslTrustStore". You can find the other command-line options under Beeline Command Options.

tusharkathpal · ‎02-25-2021

Hello @marccasajus Yes, this has been documented internally as a BUG (OPSAPS-53043) and is currently not fixed. Also, it looks you have already applied the changes which would address this.

tusharkathpal · ‎02-25-2021

Hello @SajawalSultan It seems you are running the job via user cloudera_user and it needs access to /user/<username> directory to create scratch directories which it is unable to create because user "cloudera_user" does not has permissions. hdfs:supergroup:drwxr-xr-x /user Run hdfs dfs -chmod 777 /user from hdfs user to ensure you get proper access to /user directory. Let me know if this solves your sqoop import.

tusharkathpal · ‎02-23-2021

hello @Benj1029 You need to go to the below path on the host which is hosting HIveserver2 process. cd /var/log/hive/ vi hiveserver2.log file and just before the shutdown try looking at the stack trace, the would help you with some pointers.

tusharkathpal · ‎02-18-2021

Well @ryu, My understanding is when you are storing things on HDFS and that too things related to hive, it is best to use managed table considering in mind that CDP is now coming up with compaction features where in small file issue would automatically get addressed. Compaction will not happen on external tables. one would prefer to choose external tables if the data is stored outside HDFS like S3. This is my understanding, but again it could vary on customer to customer based on their use cases.

tusharkathpal · ‎02-18-2021

Hello @ryu There is no such path as best path but obviously not /tmp location. You can create some path under /user/external_tables and further create the tables here. Again it totally depends upon you how you are designing and your use case.

tusharkathpal · ‎02-11-2021

Hello @ryu The purpose of Ranger is to give the necessary user authentication to access the tables/database. If you allow a certain user access to a particular table/database, the user will be able to perform those actions on the table/database and the unwanted user automatically will not be able to remove the table. Let say there are two users test1 and test2. If I allow test1 user to have access to table t1 and test2 user to have access to table t2, test1 will not be able to see table t2 and test2 will not be able to see test1. You can further also add granularity as to what user can perform what actions on the table. This authorization is checked via Ranger hook which is present in the Hiveserver2. Let me know if the above answers your queries.

Online	Offline
Last Visited	‎08-10-2021 10:55 AM

Member Since	‎01-25-2019 01:30 AM
Last Visited	‎08-10-2021 10:55 AM
Posts	75
Kudos received	10

Cloudera Community

Re: Sqoop Import Permission Denied

Re: Unable to Start HiveServer2 in Ambari

Re: what is the best practice on where to store hi...

Re: What is the pros and cons to having hive jobs ...

Re: SSLError CertificateError - hostname 'dev.exam...

Re: Data Node recovery after a day while under rep...

Re: Ranger error "Keystore was tampered with, or p...

Re: hiveserver2 not starting in HDP 3.1.4

Did you know that the command line options used in...

Re: Hive log rotation issue on CDH 6

Re: Sqoop Import Permission Denied

Re: Unable to Start HiveServer2 in Ambari

Re: what is the best practice on where to store hi...

Re: what is the best practice on where to store hi...

Re: What is the pros and cons to having hive jobs ...