Member since
06-03-2016
5
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1376 | 06-07-2016 09:17 AM |
02-17-2017
08:33 AM
Hi, First of all, thank you for your help. I checked the app logs but unfortunatly I don't see anything wiered. The ony thing a bit confusing is the syslog_dag of the first container looping with 2017-02-17 09:27:46,933 [INFO] [Dispatcher thread {Central}] |util.RackResolver|: Resolved <worker1_IP> to /default-rack
2017-02-17 09:27:46,933 [INFO] [Dispatcher thread {Central}] |util.RackResolver|: Resolved <worker2_IP> to /default-rack
... What excatly is the RackResolver ? Could this be dued to a issue in my network's configuration ? Bests, Orlando
... View more
02-14-2017
09:50 AM
Hi Everyone, I am facing something strange on my HDP cluster while running Hive (Tez) queries. On queries on specific ORC tables, the YARN task corresponding to the query (1) status is RUNNING, which implies that the required RAM and CPU is succesfully allocated. But the task then keeps waiting. All mappers and reducers stays in the status PENDING (2) for a long time (20 to 30 minutes), then the query starts. I know that this issue is very specific, and I read several posts similar to this situation, but whithout finding any solution. My question is : Did anyone face this situation ? Where should I look for further information ? I already looked at hiveserver2 and hivemetastore logs but nothing special shows up. Any help on this would be very apreciated. Regards, Orlando (1)
select datekey,period,count(*)
from A.t
group by datekey,period
order by datekey,period; (2)
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITED 909 0 0 909 0 0
Reducer 2 INITED 8 0 0 8 0 0
Reducer 3 INITED 1 0 0 1 0 0
--------------------------------------------------------------------------------
VERTICES: 00/03 [>>--------------------------] 0% ELAPSED TIME: 84.23 s
--------------------------------------------------------------------------------
... View more
Labels:
- Labels:
-
Apache Hive
-
Apache Tez
-
Apache YARN
06-07-2016
09:17 AM
Oh, I found my problem by looking at the datanode logs. It was an issue with my hostname resolution. Thank you for your help and your reactivity. Bests, Orlando
... View more
06-07-2016
08:03 AM
Hi @Sagar Shimpi, Thank you for your answer. Unfortunatelly, restarting the ambari-server does not fix the issue. The new added host is not appearing in Ambari's Hosts tab. Moreover, why is the datanode not present in the Namenode Web UI (on port 50070 ?) Something seems wrong with this host but I don't know where to look at. Thank you again for your help. Orlando
... View more
06-03-2016
11:14 AM
Hi everyone, I just added a new host (DataNode and NodeManager) to my HDP 2.3 cluster. Amabri successfully added the host through every steps without any warning. But in the end, I can't see my new host in the 'Hosts' tab. I can see that the number of Live Datanodes as increase in Ambari, but not in the formal Namenode Web UI (the one running on port 50070 of the Namenode). Even worst, when every mapreduce tasks are pending in ACCEPTED since YARN is unable to allocate resources on the new host. Did one of you already faced this situation ? Does anyone has a idea where I should look ? Thank you for any help. Bests, Orlando
... View more
Labels:
- Labels:
-
Apache Ambari