Apache Tez – Present and Future

© Hortonworks Inc. 2015 Page 1
Apache Tez – Present and Future
Jeff Zhang
Rajesh Balamohan

© Hortonworks Inc. 2015
Outline
•Tez Introduction
•Tez Feature Deep Dive
•Tez Improvement & Debuggability
•Tez Status & Roadmap

I/O Synchronization
Barrier
I/O Synchronization
Barrier
Job 1 ( Join a & b )
Job 3 ( Group by of c )
Job 2 (Group by of
a Join b)
Job 4 (Join of S & R )
Hive - MR
Example of MR versus Tez
Page 3
Single Job
Hive - Tez
Join a & b
Group by of a Join b
Group by of c
Job 4 (Join of S & R )

Tez – Introduction
Page 4
• Distributed execution framework
targeted towards data-processing
applications.
• Based on expressing a computation
as a dataflow graph (DAG).
• Highly customizable to meet a broad
spectrum of use cases.
• Built on top of YARN – the resource
management framework for
Hadoop.
• Open source Apache project and
Apache licensed.

What is DAG & Why DAG
Projection
Filter
GroupBy
…
Join
Union
Intersect
…
Split
…
• Directed Acyclic Graph
• Any complicated DAG can been composed of the following 3 basic
paradigm of DAG
– Sequential
– Merge
– Divide

Anatomy of DAG
Logic View
Vertex
Task_1 Task_2 Task_3
Runtime View
Task
TaskAttempt_1 TaskAttempt_2

Expressing DAG in Tez
• Logic View (DAG API )
–Allow user to express computation by using DAG
–Topological structure of the data computation flow
• Runtime API (I/P/O)
–Application logic of each computation unit
–How to move/read/write data between vertices

Logic View (DAG API)
Page 8
• Vertex (Processor, Parallelism, Resource, etc…)
• Edge (EdgeProperty)
–DataMovement
– ScatterGather (Join, GroupBy … )
– BroadCast ( Pig Replicated Join / Hive Broadcast Join )
– One2One ( Pig Order by )
– Custom

Runtime View (Runtime API)
Page 9
ProcessorInput Output
• Input
– Through which processor receives data on an edge
– One vertex can have multiple inputs
• Processor
– Application Logic (One vertex one processor)
– Consume the inputs and produce the outputs
• Output
– Through which processor write data to an edge
– One vertex can have multiple outputs
• Example of Input/Output/Processor
– MRInput & MROutput (InputFormat/OutptFormat)
– OrderedGroupedKVInput & OrderedPartitionedKVOutput (ScatterGather)
– UnorderedKVInput & UnorderedKVOutput (Broadcast & 1-1)
– PigProcessor/HiveProcessor

Benefit of DAG
• Easier to express computation in DAG
• No intermediate data written to HDFS
• Less pressure on NameNode
• No resource queuing effort & less resource contention
• More optimization opportunity with more global context

Container-Reuse
• Reuse the same container across DAG/Vertices/Tasks
• Benefit of Container-Reuse
–Reduce overhead of launching JVM
–Reduce overhead of negotiate with Resource Manager
–Reduce overhead of resource localization
–Reduced network IO
–Less resources consumed
–Object Caching

Tez Session
• Multiple Jobs/DAGs in one AM
• Container-reuse across Jobs/DAGs
• Share data between Jobs/DAGs

Dynamic Parallelism Estimation
• VertexManager
–Listen to the other vertices
status
–Coordinate and schedule its
tasks
–Communication between
vertices

ATS Integration
• Tez is fully integrated with YARN ATS (Application Timeline
Service)
–DAG Status, DAG Metrics, Task Status, Task Metrics are captured
• Diagnostics & Performance analysis
–Data Source for monitoring & diagnostics
–Data Source for performance analysis

Recovery
• AM can crash in corner cases
–OOM
–Node failure
–…
• Continue from the last checkpoint
• Transparent to end users
AM Crash

Order By of Pig
f = Load ‘foo’ as (x, y);
o = Order f by x;Sample
Aggregate
（Calculate Histogram)
HDFS
Partition
Sort
Broadcast
Load &
Sample
Aggregate
（Calculate Histogram)
Partition
Sort
1-1
ScatterGather
ScatterGather

• Performance
–Speculation
–Better use of JVM Memory
–Intermediate File Improvements
–Shuffle Improvements
• Debuggability
–Job Analysis Tools
–Shuffle Performance Analysis Tool
–Local Mode
–Tez UI

Speculation
• Maintains Periodic Runtime Statistics of Tasks
• Similar to Legacy MR speculation
–Trigger speculative attempt when estimated runtime > mean runtime
• Good for Cluster Having Good & Slow Nodes.
• <TBD>

Intermediate File Format Improvements
• Key value format used for storing
intermediate format in Tez
• Drawbacks of earlier format
–Needs larger buffer in memory (due to
duplicate keys)
–Unwanted key comparison of identical
keys during merge sort
–Bigger file size in disk
–Not ideal for all use cases
• New Intermediate File Format
–Works based on (K, List<V>)
–Lesser key comparisons during merge
sort
–Provides 57% memory efficiency and
23% improvement in disk storage
Task
Spill 1 Spill 2 Spill 3
Merged Spill
Key
Len
Value Len Key Bytes Value Bytes
Key
Len
Key
Len
Key
Len
………………………
EOF Marker
Key
Len
Key Bytes Value Len Value Bytes V_END
Key
Len
Key
Len
Key
Len
EOF Marker
………………………
…
…
…
Old IFile Format
New IFile Format
RLE
RLE
RLE

Better use of JVM Memory
• PipelinedSorter can support > 2 GB sort buffers
–Containers with higher RAM no longer limited by 2 GB sort buffer limits
–Avoids unnecessary spills
• Reduced key comparison costs in PipelinedSorter
• <TBD>

Better use of JVM Memory - Contd
• BytesWritable Improvements
–Provides FastByteSerialization
–Saves 8 bytes per key-value pair
–Reduces IFile size by 25%
–Reduces SERDE costs
• WeightbedMemoryDistributor
for better memory management
in tasks
–Observed 26% runtime
improvements
• Enabled RLE in reducer codepath
–Improved Job Runtime
–Reduced IO Cost
• <TBD>

Source Task
….
….
Broadcast Shuffle Improvements
Task 1
Task 2
Task N
…
Task 1
Task 2
Task N
…
Task 1
Task 2
Task N
…
Broadcast
From local disk
From local disk
Source Task
….
….
Task 1
Task 2
Task N
…
Task 1
Task 2
Task N
…
Task 1
Task 2
Task N
…
Broadcast
Before Fix After Fix

PipelinedShuffle Improvments
• Final merge in source
task is avoided.
– Less IO
• Consumers are
informed about spill
events in advance
– Better usage of
network bandwidth
– Overlap CPU with
network
– For sorted/unsorted
outputs, send data to
consumers in chunks
• Observed 20% runtime
improvement in
queries involving heavy
skews
Task 1
Spill 1
Task 2
Reduce Task 1 Reduce Task 1Reduce Task 1Reduce Task 1Reduce Task N
…..
…..
…..
…..
Task 1
Spill 1
Task 2
Reduce Task 1 Reduce Task 1Reduce Task 1Reduce Task 1Reduce Task N
…..
…..
…..
…..
Merged Spill
Normal Shuffle Path
Pipelined Shuffle Path

Job Analysis Tools
• DAG Swimlane
–“$TEZ_HOME/tez-tools/swimlanes/sh yarn-swimlanes.sh <app_id>”
Prewarm
Container Reuse
Remote Reads

Shuffle Performance Analysis Tools
• Analyze shuffle performance between source / destination
nodes

Better Debuggability– Local Mode
• Test Tez Jobs without Hadoop Cluster
• Enables Fast Prototyping
• Fast Unit Testing
• Runs on Single JVM (easy for debugging)
• Scheduling / RPC invocations Skipped

Better Debuggability- Tez-UI

Better Debuggability - Tez-UI

RoadMap
• Shared Output Edges
• Multiple Edges between Vertices
• Local Mode Stabilization
• Optimizing (include/exclude) Vertex at Runtime
• <TBD>

Tez – Adoption
• Apache Hive
• Start from Hive 0.13
• set hive.exec.engine = tez
• Apache Pig
• Start from Pig 0.14
• pig -x tez
• Cascading
• Cascading 3.0 WIP
Page 35

Thank You!
Questions & Answers
Page 36

Apache Tez – Present and Future

More Related Content

What's hot

Viewers also liked

Similar to Apache Tez – Present and Future

More from DataWorks Summit

Recently uploaded

Apache Tez – Present and Future

Editor's Notes