Member since
01-25-2019
75
Posts
10
Kudos Received
13
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2273 | 02-25-2021 02:10 AM | |
1101 | 02-23-2021 11:31 PM | |
2041 | 02-18-2021 10:18 PM | |
2917 | 02-11-2021 10:08 PM | |
15037 | 02-01-2021 01:47 PM |
08-10-2021
07:34 AM
Hello @Moudma Rstudio is an application which I guess might be running on windows or mac OS. On these OS you will be downloading the ODBC application where you configure the DSN parameters. Under that configuration only, there is an Advanced Option where you will find the properties.
... View more
08-10-2021
12:45 AM
Hello @Moudma Open the ODBC application in Windows and click on any one of the DSN and further click on Advanced Options... to get the above window. Regards, Tushar
... View more
06-16-2021
12:57 AM
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
... View more
05-20-2021
04:44 AM
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.
... View more
05-20-2021
04:40 AM
@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.
... View more
05-20-2021
04:39 AM
1 Kudo
-Try the below. -When you start the HS2, track the logs and look for the first error in HS2. -Parallelly ensure that your zookeeper is up and running and check the zk logs during the restart to validate if the connections are coming to ZK and whether zk is accepting or rejecting the connection.
... View more
05-14-2021
06:39 AM
Hello @snm1523 Could you please help me with the below details. Step 1: Connect to any of the edge node and run the below. id -Gn <new username> kinit <username> connect to HS2 using the jdbc conn string and then run, select current_user(); run the query select * from tablename which gives error. Step 2: Now from the same edge node, connect to one of the impala node. id -Gn <new username> kinit <username> Connect to Impala using the jdbc connection string beeline -u "jdbc:hive2://<impala-coordinator-node>:21050/default;principal=impala/<LB FQDN NAME>@REALM_NAME;ssl=true;sslTrustStore=<truststore path>; **Use LB FQDN Name in principal section if you have LB else use the coordinator FQDN hostname above. If you have ssl enabled then use:-->sslTrustStore=<truststore path> else you can remove from connection string. and run , select current_user(); and run the same query here. Step 3: ssh to host running Hue server. If you have multiple host running hue server then ssh to them one by one and repeat the same. id -Gn <username> output kinit username connect once to HS2 and Impala each via beeline then run select current_user() and the query. Once done share all the results to validate things.
... View more
05-13-2021
02:59 PM
Hello @snm1523 First and for most thing, ensure the users are synced in all the nodes. for all the newly added users run id -Gn <username> on all the impala and hs2 nodes and ensure that this matches across all the nodes.
... View more
05-13-2021
02:52 PM
Hello @Charles25 I would like to see the HS2 logs when the connection is being initiated. Need to understand why is the HS2 rejecting connections if the connection from client is hitting HS2.
... View more
05-10-2021
11:26 PM
Issue
Partition discovery such as "metastore.partition.management.task.frequency" and "partition.retention.period" does not take effect in Hive if metastore.compactor.initiator.on is not turned on by default on HMS. The same property is responsible for activating Hive Metastore background tasks which involves partition discovery as well.
Resolution
To ensure partition discovery works as expected, do the following:
Go to CM > Hive >Configuration.
Search for Hive Metastore Server Advanced Configuration Snippet (Safety Valve) for hive-site.xml.
Click on + >Add the following: Name :--> metastore.compactor.initiator.on
Value :--> true
Save the changes and restart.
Ensure the tables have the property discover.partitions is set to True for certain tables.
... View more
Labels: