Hello pooja From your stack trace your table seems to be bucketed. Can you share your table definition could you also try running the query with the setting: hive.auto.convert.join.noconditionaltask=false ... View more

Hello Michel Right now the Hive plan calculation does not reach out to get Hbases stats so currently no added benefit from the Hbase stats. This being said these are questions that are being worked on in different initiatives, so this will likely change in the future. ... View more

The warning DFSInputStream has been closed already is a warning and is fixed in hadoop 2.7.2 : https://issues.apache.org/jira/browse/HDFS-8099 taking 10 minutes to submit the job seems to be another problem from your reduce issue. Do check what your available ressources look like in yarn and how long it takes to get an Application master. i t would interesting in the logs to see if he is waiting or what else is happening. You could also check it your timeline server is responding and not underwater as it could have impacts ... View more

Hello Venkadesh It would be worth investigating why your reducer gets a time out error and then gets completed. Do you have a slow node, is a code related error, are your reducers sitting around too long. According to those questions many options are available - you could increase the task timeout, (mapred.task.timeout) - you could force increase the number of reducers to get better distribution (mapred.reduce.tasks=# of reducers) -you could configure when reducers start get to start clsoer to the end of the map phase (mapred.reduce.slowstart.completed.maps) - you could have speculative execution to see if some nodes are faster then others: These are some ideas that come to mind, depending on a closer analysis their might also be other ways. hope any of this helps ... View more

can you make sure tt the top of the tutorial page, open the gear icon and make sure "hive %hive..." is blue and click save. If not can you share the description and config of your hive interpreter ... View more

In order to use node labels you will first have to enable them in yarn: yarn.node-labels.enabled true then set up a label directory, create labels and associate to hosts and queue. Labels are logically accessed through the capacity queue they are associated with. In your case it would just be running your job in the right yarn capacity queue. The documentation has an example that can help you: https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.2/bk_yarn_resource_mgt/content/configuring_node_labels.html ... View more

hello Sumit If your ulimit is already set to unlimited or a very high number, you could actually getting insight on the number of open files with lsof | wc -l. You may need to increase the max number of filed handles in the os. check fs.file-max to see if this helps. this is to try to solve the cause. An offlineMetaRepair, fix meta should help with the consequence. ... View more