Member since
06-21-2017
16
Posts
3
Kudos Received
0
Solutions
05-03-2018
08:37 AM
@Neeraj Sabharwal , I am not able to see the parameter to set the ldap bind password for base DN for hive . Where to find this parameter.
... View more
10-02-2017
05:29 AM
@Prakash Punj, Can you check if any of the filesystem got full / any of your disks become bad.
... View more
07-23-2017
04:49 PM
Try adding the jars as extra classpath with option --driver-class-path.
... View more
07-22-2017
08:11 AM
Can u try with spark submit command to run the examples. Ref:- Spark-submit command
... View more
07-20-2017
05:44 PM
@Srinivas, Does all your datanode is affected by this issues / SIngle DataNode is only affected. Have u tried to re-balance HDFS to see if issue is fixed.
... View more
07-07-2017
04:34 AM
Hi, Can u reset the ambari-agent in all servers and try to register. amabri-agent reset <Ambari_host_name>
... View more
07-07-2017
04:18 AM
2 Kudos
@rama TEZ Engine first allocates memory in the cluster , then it lauches the hive cli, If you launching hive in TEZ engine, Check if any jobs in accepted state . This is the reason hive is not able to launch TEZ Engine , if you enable the debug the logs , you can able to see where it got stuck.
... View more
07-06-2017
07:07 PM
1 Kudo
Hi, Check free memory is present in the client node . if it is a kerberized cluster , Ensure you have a valid ticket. Still if you have not got clue, Launch the hive cli with debug mode and check the debug logs. hive -hiveconf hive.log.file=debug_hive.log -hiveconf hive.log.dir=/tmp/hiveCLI -hiveconf hive.root.logger=DEBUG,DRFA
... View more
06-29-2017
07:54 PM
Hi Saurab, Are u able to see the changed value in the logs , while restarting the namenode. you can check in the namenode startup logs like. grep -ri dfs.replication *
... View more
06-24-2017
03:26 AM
Set SPARK_MASTER_PORT = 35994 in spark-env.sh , and restart the spark . If you are not able to pass the port test with sample port , then it is the filrewall issue. what is the o/p of the test. On server end(where driver runs):-
nc -l 35994
On client end(where worker runs):-
nc -vz <server-ip> 35994
... View more