[HIVE-4679] WebHCat can deadlock Hadoop if the number of concurrently running tasks if higher or equal than the number of mappers

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.10.0
• Fix Version/s: 0.12.0
• Component/s: HCatalog
• Assignee: Eugene Koifman
• Reporter: Eugene Koifman
• Created: 06/Jun/13 21:22
• Updated: 01/Oct/19 22:07
• Resolved: 18/Jun/13 23:45

Description

o In the current Templeton design, each time a Job is submitted thru the REST API (it can be Pig/Hive or MR job), it will consume one Hadoop map slot. Given that the number of map slots is finite in the cluster (16 node cluster will have 32 map slots), in some circumstances, a user can deadlock the cluster if Templeton job submission pipeline takes over all map slots (Templeton map tasks will wait for the actual underlying jobs to complete, what will never happen, given that Hadoop has no free map slots to schedule new tasks).

o HCat queries use a different mechanism and do not contribute to the deadlock.

Issue Links

• is related to: HIVE-4725 templeton.hadoop.queue.name property should be documented