1.6.1

bin packing example application UI

Details for Stage 0 (Attempt 0)

DAG Visualization
Show Additional Metrics
Event Timeline
Enable zooming
Scheduler DelayTask Deserialization TimeShuffle Read TimeExecutor Computing TimeShuffle Write TimeResult Serialization TimeGetting Result Time
?
?
?
?
?
1 / ip-172-28-22-41.ap-southeast-2.compute.internal
2 / ip-172-28-207-11.ap-southeast-2.compute.internal
3 / ip-172-28-203-39.ap-southeast-2.compute.internal
4 / ip-172-28-17-185.ap-southeast-2.compute.internal
0
0
11:05
Thu 30 June
11:10
11:15
11:20
11:25
11:30
11:35
11:40
11:45
11:50
11:55

Summary Metrics for 38 Completed Tasks

MetricMin25th percentileMedian75th percentileMax
Duration13 s42 s2.7 min7.0 min48 min
Scheduler Delay8 ms29 ms39 ms0.3 s0.3 s
Task Deserialization Time 20 ms40 ms58 ms4 s4 s
GC Time 0.5 s3 s12 s30 s2.6 min
Result Serialization Time 0 ms0 ms0 ms0 ms1 ms
Getting Result Time 0 ms0 ms0 ms0 ms0 ms
Peak Execution Memory 0.0 B0.0 B0.0 B0.0 B0.0 B
Input Size / Records0.0 B / 60.0 B / 618.8 KB / 653.4 KB / 6311.2 KB / 6
Output Size / Records749.7 KB / 65.8 MB / 626.2 MB / 682.6 MB / 6528.8 MB / 6

Aggregated Metrics by Executor

Executor ID ▴ Address Task Time Total Tasks Failed Tasks Succeeded Tasks Input Size / Records Output Size / Records
1 CANNOT FIND ADDRESS 27 min 8 0 8 138.7 KB / 48 300.7 MB / 48
2 CANNOT FIND ADDRESS 39 min 8 0 8 222.0 KB / 48 391.6 MB / 48
3 CANNOT FIND ADDRESS 1.1 h 12 0 12 443.6 KB / 72 752.5 MB / 72
4 ip-172-28-17-185.ap-southeast-2.compute.internal:45315 1.5 h 10 0 10 565.3 KB / 60 976.4 MB / 60

Tasks

Index  ▴ ID Attempt Status Locality Level Executor ID / Host Launch Time Duration Scheduler Delay Task Deserialization Time GC Time Result Serialization Time Getting Result Time Peak Execution Memory Input Size / Records Output Size / Records Errors
0 0 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:06:20 13 s 0.3 s 4 s 0.5 s 1 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 749.7 KB / 6
1 1 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:06:20 16 s 0.3 s 4 s 0.5 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 1278.6 KB / 6
2 2 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:06:20 16 s 0.3 s 4 s 0.5 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 1007.9 KB / 6
3 3 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:06:20 18 s 0.3 s 4 s 0.5 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 1695.2 KB / 6
4 4 0 SUCCESS RACK_LOCAL 4 / ip-172-28-17-185.ap-southeast-2.compute.internal 2016/06/30 01:06:21 23 s 0.3 s 4 s 0.9 s 1 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 2.3 MB / 6
5 5 0 SUCCESS RACK_LOCAL 4 / ip-172-28-17-185.ap-southeast-2.compute.internal 2016/06/30 01:06:21 26 s 0.3 s 4 s 1 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 3.1 MB / 6
6 6 0 SUCCESS RACK_LOCAL 4 / ip-172-28-17-185.ap-southeast-2.compute.internal 2016/06/30 01:06:21 32 s 0.3 s 4 s 1 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 4.4 MB / 6
7 7 0 SUCCESS RACK_LOCAL 4 / ip-172-28-17-185.ap-southeast-2.compute.internal 2016/06/30 01:06:21 36 s 0.3 s 4 s 1 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 4.4 MB / 6
8 8 0 SUCCESS RACK_LOCAL 1 / ip-172-28-22-41.ap-southeast-2.compute.internal 2016/06/30 01:06:21 41 s 0.3 s 4 s 2 s 1 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 4.4 MB / 6
9 9 0 SUCCESS RACK_LOCAL 1 / ip-172-28-22-41.ap-southeast-2.compute.internal 2016/06/30 01:06:21 42 s 0.3 s 4 s 3 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 5.8 MB / 6
10 10 0 SUCCESS RACK_LOCAL 1 / ip-172-28-22-41.ap-southeast-2.compute.internal 2016/06/30 01:06:21 54 s 0.3 s 4 s 3 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 8.7 MB / 6
11 11 0 SUCCESS RACK_LOCAL 1 / ip-172-28-22-41.ap-southeast-2.compute.internal 2016/06/30 01:06:21 57 s 0.3 s 4 s 3 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 9.6 MB / 6
12 12 0 SUCCESS RACK_LOCAL 2 / ip-172-28-207-11.ap-southeast-2.compute.internal 2016/06/30 01:06:22 1.4 min 0.3 s 4 s 6 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 9.4 MB / 6
13 13 0 SUCCESS RACK_LOCAL 2 / ip-172-28-207-11.ap-southeast-2.compute.internal 2016/06/30 01:06:22 1.4 min 0.3 s 4 s 6 s 1 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 14.8 MB / 6
14 14 0 SUCCESS RACK_LOCAL 2 / ip-172-28-207-11.ap-southeast-2.compute.internal 2016/06/30 01:06:22 1.7 min 0.3 s 4 s 7 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 17.0 MB / 6
15 15 0 SUCCESS RACK_LOCAL 2 / ip-172-28-207-11.ap-southeast-2.compute.internal 2016/06/30 01:06:22 1.9 min 0.3 s 4 s 7 s 0 ms 0 ms 0.0 B 0.0 B (hadoop) / 6 19.7 MB / 6
16 16 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:06:38 1.9 min 39 ms 58 ms 10 s 0 ms 0 ms 0.0 B 15.3 KB (hadoop) / 6 22.5 MB / 6
17 17 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:06:41 2.0 min 36 ms 56 ms 10 s 0 ms 0 ms 0.0 B 15.9 KB (hadoop) / 6 22.1 MB / 6
18 18 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:06:41 2.2 min 38 ms 47 ms 11 s 0 ms 0 ms 0.0 B 22.9 KB (hadoop) / 6 26.2 MB / 6
19 19 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:06:43 2.7 min 33 ms 30 ms 12 s 0 ms 0 ms 0.0 B 18.1 KB (hadoop) / 6 30.5 MB / 6
20 20 0 SUCCESS RACK_LOCAL 4 / ip-172-28-17-185.ap-southeast-2.compute.internal 2016/06/30 01:06:48 2.8 min 41 ms 44 ms 15 s 0 ms 0 ms 0.0 B 18.8 KB (hadoop) / 6 25.0 MB / 6
21 21 0 SUCCESS RACK_LOCAL 4 / ip-172-28-17-185.ap-southeast-2.compute.internal 2016/06/30 01:06:51 3.1 min 35 ms 43 ms 16 s 0 ms 0 ms 0.0 B 19.8 KB (hadoop) / 6 35.2 MB / 6
22 22 0 SUCCESS RACK_LOCAL 4 / ip-172-28-17-185.ap-southeast-2.compute.internal 2016/06/30 01:06:57 3.5 min 34 ms 40 ms 17 s 0 ms 0 ms 0.0 B 26.1 KB (hadoop) / 6 42.4 MB / 6
23 23 0 SUCCESS RACK_LOCAL 4 / ip-172-28-17-185.ap-southeast-2.compute.internal 2016/06/30 01:07:01 4.2 min 24 ms 39 ms 18 s 0 ms 0 ms 0.0 B 24.6 KB (hadoop) / 6 51.4 MB / 6
24 24 0 SUCCESS RACK_LOCAL 1 / ip-172-28-22-41.ap-southeast-2.compute.internal 2016/06/30 01:07:07 5.2 min 27 ms 43 ms 24 s 0 ms 0 ms 0.0 B 29.5 KB (hadoop) / 6 55.2 MB / 6
25 25 0 SUCCESS RACK_LOCAL 1 / ip-172-28-22-41.ap-southeast-2.compute.internal 2016/06/30 01:07:08 5.8 min 25 ms 41 ms 26 s 0 ms 0 ms 0.0 B 34.3 KB (hadoop) / 6 55.4 MB / 6
26 26 0 SUCCESS RACK_LOCAL 1 / ip-172-28-22-41.ap-southeast-2.compute.internal 2016/06/30 01:07:20 6.4 min 39 ms 49 ms 28 s 0 ms 0 ms 0.0 B 38.8 KB (hadoop) / 6 69.8 MB / 6
27 27 0 SUCCESS RACK_LOCAL 1 / ip-172-28-22-41.ap-southeast-2.compute.internal 2016/06/30 01:07:23 6.3 min 27 ms 40 ms 28 s 0 ms 0 ms 0.0 B 35.9 KB (hadoop) / 6 91.8 MB / 6
28 28 0 SUCCESS RACK_LOCAL 2 / ip-172-28-207-11.ap-southeast-2.compute.internal 2016/06/30 01:07:53 7.0 min 30 ms 45 ms 30 s 0 ms 0 ms 0.0 B 54.5 KB (hadoop) / 6 64.1 MB / 6
29 29 0 SUCCESS RACK_LOCAL 2 / ip-172-28-207-11.ap-southeast-2.compute.internal 2016/06/30 01:07:53 7.6 min 30 ms 64 ms 30 s 0 ms 0 ms 0.0 B 54.2 KB (hadoop) / 6 82.6 MB / 6
30 30 0 SUCCESS RACK_LOCAL 2 / ip-172-28-207-11.ap-southeast-2.compute.internal 2016/06/30 01:08:07 8.2 min 29 ms 46 ms 33 s 0 ms 0 ms 0.0 B 60.0 KB (hadoop) / 6 83.8 MB / 6
31 31 0 SUCCESS RACK_LOCAL 2 / ip-172-28-207-11.ap-southeast-2.compute.internal 2016/06/30 01:08:23 9.6 min 25 ms 63 ms 35 s 0 ms 0 ms 0.0 B 53.4 KB (hadoop) / 6 100.3 MB / 6
32 32 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:08:34 11 min 29 ms 30 ms 53 s 0 ms 0 ms 0.0 B 76.2 KB (hadoop) / 6 116.3 MB / 6
33 33 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:08:41 13 min 25 ms 20 ms 1.1 min 0 ms 0 ms 0.0 B 104.6 KB (hadoop) / 6 161.4 MB / 6
34 34 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:08:54 15 min 30 ms 24 ms 1.2 min 0 ms 0 ms 0.0 B 72.0 KB (hadoop) / 6 178.4 MB / 6
35 35 0 SUCCESS RACK_LOCAL 3 / ip-172-28-203-39.ap-southeast-2.compute.internal 2016/06/30 01:09:23 18 min 28 ms 22 ms 1.3 min 0 ms 0 ms 0.0 B 118.5 KB (hadoop) / 6 190.5 MB / 6
36 36 0 SUCCESS RACK_LOCAL 4 / ip-172-28-17-185.ap-southeast-2.compute.internal 2016/06/30 01:09:33 24 min 8 ms 20 ms 1.1 min 1 ms 0 ms 0.0 B 164.8 KB (hadoop) / 6 279.5 MB / 6
37 37 0 SUCCESS RACK_LOCAL 4 / ip-172-28-17-185.ap-southeast-2.compute.internal 2016/06/30 01:10:00 48 min 26 ms 32 ms 2.6 min 0 ms 0 ms 0.0 B 311.2 KB (hadoop) / 6 528.8 MB / 6