Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Hive's taking to much time. It is normal?

avatar
Contributor

Hi,

I'm trying to do a select count(*) from tweets; using Hive CLI. But as you can see, it is taking to much time (i guess)

It is normal?

Any tip?

10007-hive-sql.png

Regards

1 ACCEPTED SOLUTION

avatar
Rising Star
hide-solution

This problem has been solved!

Want to get a detailed solution you have to login/registered on the community

Register/Login
14 REPLIES 14

avatar
Contributor

Never mind about cluster size. I saw you are using sandbox. Probably job cannot be started because there is not enough resource. You can try allocate more memory for VM or decrease tez container size.

avatar
Contributor

Zyang, what is the purpose about decreasing Tez Container Size?

avatar
Contributor

Your resource is limited. To solve the problem, either you allocate more resource or just request ask fro resource.

avatar
Contributor

Well Zyang, as you suggested i tried decreasing tez container size.

Now i got the following error

Vertex did not succeed due to OWN_TASK_FAILURE, failedTasks:1 killedTasks:0, Vertex vertex_1480577643003_0005_1_00 [Map 1] killed/failed due to:OWN_TASK_FAILURE]Vertex killed, vertexName=Reducer 2, vertexId=vertex_1480577643003_0005_1_01, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to OTHER_VERTEX_FAILURE, failedTasks:0 killedTasks:1, Vertex vertex_1480577643003_0005_1_01 [Reducer 2] killed/failed due to:OTHER_VERTEX_FAILURE]DAG did not succeed due to VERTEX_FAILURE. failedVertices:1 killedVertices:1

Any suggestion?

regards

avatar
Contributor

Map vertex get killed because Reduce vertex failed. Any log for reduce vertex?