mapreduce - Map-Reduce Logs on Hive-Tez -
i want interpretation of map-reduce logs after running query on hive-tez ? lines after info: conveys ? here have attached sample
info : session open info : dag name: select a.model...) info : tez session closed. reopening... info : session re-established. info : info : status: running (executing on yarn cluster app id application_14708112341234_1234) info : map 1: -/- map 3: -/- map 4: -/- map 7: -/- reducer 2: 0/15 reducer 5: 0/26 reducer 6: 0/13 info : map 1: -/- map 3: 0/118 map 4: 0/118 map 7: 0/1 reducer 2: 0/15 reducer 5: 0/26 reducer 6: 0/13 info : map 1: 0/118 map 3: 0/118 map 4: 0/118 map 7: 0/1 reducer 2: 0/15 reducer 5: 0/26 reducer 6: 0/13 info : map 1: 0/118 map 3: 0/118 map 4: 0(+5)/118 map 7: 0/1 reducer 2: 0/15 reducer 5: 0/26 reducer 6: 0/13 info : map 1: 0/118 map 3: 0(+5)/118 map 4: 0(+7)/118 map 7: 0(+1)/1 reducer 2: 0/15 reducer 5: 0/26 reducer 6: 0/13 info : map 1: 0/118 map 3: 0(+15)/118 map 4: 0(+18)/118 map 7: 0(+1)/1 reducer 2: 0/15 reducer 5: 0/26 reducer 6: 0/13
the log posted dag execution log. dag consists of map 1,map 3,map 4,map 7 mappers vertices , reducers: reducer 2,reducer 5,reducer 6
info : map 1: -/-
means vertex not initialized, number of mappers not calculated yet.
map 4: 0(+7)/118
- means totally there 118 mappers, 7 of them running in parallel, 0 completed yet, 118-7=111 pending.
reducer 2: 0/15 - means totally there 15 reducers, 0 of them running, 0 of them completed (15 reducers pending).
negative figures (there no such in example) = number of failed or killed mappers or reducers
Comments
Post a Comment