Managing growth in Production Hadoop Deployments презентация

Содержание

ALTISCALE : INFRASTRUCTURE NERDS Soam Acharya - Head of Application Engineering Formerly Chief Scientist @ Limelight OVP, Yahoo Research Engineer Charles Wimmer, Head of Operations Former Yahoo! & LinkedIn SRE Managed

Слайд 1MANAGING GROWTH IN PRODUCTION HADOOP DEPLOYMENTS
Soam Acharya
@soamwork
Charles Wimmer
@cwimmer
Altiscale
@altiscale
HADOOP SUMMIT 2015
SAN JOSE

Слайд 2ALTISCALE : INFRASTRUCTURE NERDS
Soam Acharya - Head of Application Engineering
Formerly Chief

Scientist @ Limelight OVP, Yahoo Research Engineer
Charles Wimmer, Head of Operations
Former Yahoo! & LinkedIn SRE
Managed 40000 nodes in Hadoop clusters at Yahoo!
Hadoop as a Service, built and managed by Big Data, SaaS, and enterprise software veterans
Yahoo!, Google, LinkedIn, VMWare, Oracle, ...

Слайд 3SO, YOU’VE PUT TOGETHER YOUR FIRST HADOOP DEPLOYMENT
It’s now running production

ETLs

Слайд 4CONGRATULATIONS!

Слайд 5BUT THEN ...
Your data scientists get on the cluster and start

building models

Слайд 6BUT THEN ...
Your data scientists get on the cluster and start

building models
Your BI team starts running interactive SQL on Hadoop queries ..

Слайд 7BUT THEN ...
Your data scientists get on the cluster and start

building models
Your BI team starts running interactive SQL on Hadoop queries ..
Your mobile team starts sending RT events into the cluster ..


Слайд 8BUT THEN ...
Your data scientists get on the cluster and start

building models
Your BI team starts running interactive SQL on Hadoop queries ..
Your mobile team starts sending RT events into the cluster ..
You sign up more clients
And the input data for your initial use case doubles ..


Слайд 9SOON, YOUR CLUSTER ...

Слайд 10AND YOU …

Слайд 11THE “SUCCESS DISASTER” SCENARIO
Initial success
Many subsequent use cases on cluster
Cluster gets

bogged down

Слайд 12WHY DO CLUSTERS FAIL?
Failure categories:
Too much data
Too many jobs
Too many users

Слайд 13HOW EXTRICATE YOURSELF?
Short term strategy:
Get more resources for your cluster
Expand cluster

size!
More headroom for longer term strategy
Longer term strategy

Слайд 14LONGER TERM STRATEGY
Can’t cover every scenario
Per failure category:
Selected pressure points (PPs)
Can

occur at different levels of Hadoop stack
Identify and shore up pressure points
Squeeze more capacity from cluster



Слайд 15HADOOP 2 STACK REMINDER




Application Layer
Execution Framework
Core Hadoop Layer
Machine Level

Слайд 16FAILURE CATEGORY 1 - TOO MUCH DATA
PP: HDFS at capacity
PP: Too

many objects

Слайд 17PRESSURE POINT - HDFS AT CAPACITY
Unpredictable cluster behavior
Transient errors
Hadoop daemons can’t

save logs to HDFS
Execution framework errors:
Hive unable to run queries that create temp tables

Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: org.apache.hadoop.ipc.RemoteException(java.io.IOException): File /tmp/hive-user/hive_2014-07-23_08-43-40_408_2604848084853512498-1/_task_tmp.-ext-10001/_tmp.000121_0 could only be replicated to 1 nodes instead of minReplication (=2). There are xx datanode(s) running and no node(s) are excluded in this operation.


Слайд 18HDFS AT CAPACITY MITIGATION
Use HDFS quotas!

hdfs dfsadmin -setSpaceQuota 113367670 /

Quotas can

be set per directory
Cannot be set per user
Protection against accidental cluster destabilzation

Слайд 19TOO MANY OBJECTS
“Elephants are afraid of mice. Hadoop is afraid of

small files.”


# of dirs + files

# of blocks

Слайд 20TOO MANY OBJECTS

Memory pressure:
Namenode heap: too many files + directories +

objects in HDFS
Datanode heap: too many blocks allocated per node

Performance overhead
Too much time spent on container creation and teardown
More time spent in execution framework than actual application

Слайд 21WHERE ARE THE OBJECTS?
Use HDFS count:

hdfs dfs -count -q

Number

of directories, files and bytes
On per directory basis

Use fsimage files:

Can be produced by NN

hdfs oiv

Detailed breakdown of the HDFS file system
Hard!


Слайд 22TOO MANY OBJECTS - MITIGATION
Short term:
Increase NN/DN heapsizes
Node physical limits
Increase cluster

node count

Longer term:
Find and compact
Coalesce multiple files
Use HAR

Слайд 23COALESCE MULTIPLE FILES I
Hadoop streaming job






Whatever Hadoop can read on cluster


LZO output

hadoop \ jar /opt/hadoop/share/hadoop/tools/lib/hadoop-streaming-*.jar \ -D mapreduce.job.reduces=40 \ -D mapred.output.compress=true \ -D mapred.output.compression.codec=\ com.hadoop.compression.lzo.LzopCodec \ -D mapreduce.output.fileoutputformat.compress.type=BLOCK \ -D mapreduce.reduce.memory.mb=8192 \ -mapper /bin/cat \ -reducer /bin/cat \ -input $IN_DIR \ -output $DIR

Слайд 24COALESCE MULTIPLE FILES II
Build index for LZO output
Tell hadoop where the

splits are

hadoop \ jar /opt/hadoop/share/hadoop/common/lib/hadoop-lzo-*.jar \ com.hadoop.compression.lzo.DistributedLzoIndexer \ $DIR

Слайд 25COMBINE FILES INTO HAR
HAR: Hadoop Archive
hadoop archive -archiveName .har -p

...
MR job to produce archive
Watch out for replication factor
On versions 2.4 and earlier, source files are set to a default replication factor 10
Not good for small clusters
-r option added in 2.6

Слайд 26COMBINE FILES INTO HAR
HAR archives are useful if you want to

preserve the file/directory structure of input

[alti_soam@desktop ~]$ hdfs dfs -ls har:///tmp/alti_soam_test.har Found 3 items drwxr-xr-x - alti_soam hdfs 0 2013-09-03 22:44 har:/tmp/alti_soam_test.har/examples drwxr-xr-x - alti_soam hdfs 0 2013-11-16 03:53 har:/tmp/alti_soam_test.har/test-pig-avro-dir drwxr-xr-x - alti_soam hdfs 0 2013-11-12 22:23 har:/tmp/alti_soam_test.har/test-camus

Слайд 27FAILURE CATEGORY 2 - TOO MANY JOBS
“Help! My job is stuck!”
Jobs

don’t make progress
Jobs don’t start
“Right” jobs finish last
Mixed profile job issues

Слайд 28TOO MANY JOBS REMEDIATION
Need to quantify job processing on cluster
Hadoop job

usage analysis:
Resource Manager logs
History Server logs, job history files
APIs
Analysis goals:
Queue usage => cluster utilization
Time spent by jobs/containers in waiting state
Job level stats
# of jobs, type of jobs …
Queue tuning

Слайд 29HADOOP LOGS - RESOURCE MANAGER
job stats (outcome, duration, startdate)

queue used

container:
number allocated
Memory,

vCPU allocation
state transition times
outcome


Слайд 30HADOOP LOGS - JOBHISTORY FILES
Configure history server to produce files

Created for

every MR job
HDFS data volume processed
for mappers/reducers:
CPU time
memory used
start/end time
max parallel maps, reduces
GC time

not available for Tez/Spark:
Use timeline server for better logging
Timeline server dependencies

Слайд 31HADOOP LOG ANALYSIS
Analysis goals:
Queue usage => cluster utilization
Time spent by jobs/containers

in waiting state
Job level stats:
# of jobs
Failed/killed vs successful
Type of jobs
Container level stats
How analyze logs?
Custom scripts
Parse job history files, hadoop logs
Data warehouse
Visualization
Not much by the way of publicly available tools

Слайд 32SAMPLE PLOT: CONTAINER WAIT TIME AND UTILIZATION PER QUEUE
Container wait times
Queue

utilization

vCore usage

Слайд 33SAMPLE PLOT: DAILY JOB TYPE AND STATUS

Слайд 34SAMPLE PLOT: DAILY JOB BREAKDOWN BY USER

Слайд 35QUEUE TUNING STRATEGY
Determine how you want your cluster to behave
Pick scheduler

depending on behavior

Real world examples:
Production jobs must get resources
Dedicate a certain portion of the cluster regardless of cluster state (idle, at capacity)
Data loading jobs
Constrain to a small portion of cluster to preserve network bandwidth
Research jobs:
Small portion of cluster at peak
Large portion of cluster when idle
Divide up cluster amongst business units

Слайд 36QUEUE TUNING - SCHEDULER BASICS

Слайд 37MORE ON EACH SCHEDULER
Fair Scheduler:
Hadoop Summit 2009
Job Scheduling With the

Fair and Capacity Schedulers - Matei Zaharia
Capacity Scheduler:
Hadoop Summit 2015 (5/9, 12:05pm)
Towards SLA-based Scheduling on YARN - Sumeet Singh, Nathan Roberts

Слайд 38TOO MANY JOBS - MIXED PROFILE JOBS
Jobs may have different memory

profiles
Standard MR jobs: small container sizes
Newer execution frameworks (Spark, H2O):
Large container sizes
All or nothing scheduling
A job with many little tasks
Can starve jobs that require large containers

Слайд 39TOO MANY JOBS - MIXED PROFILE JOBS MITIGATION
Reduce container sizes if

possible
Always start with the lowest container sizes
Node labels (YARN-2492) and gang scheduling (YARN-624)
More details:
Running Spark and MapReduce Together In Production - David Chaiken
Hadoop Summit 2015, 06/09, 2:35pm

Слайд 40TOO MANY JOBS - HARDENING YOUR CLUSTER
Cluster configuration audit
Container vs heap

size



Appropriate kernel level configuration
Turn on Linux Container Executor
Enable Hadoop Security
Use operating system cgroups
Protect Hadoop daemons
Cage user processes:
Impala
Limits on what Hadoop can control:
CPU
But not memory, network & disk BW


mapreduce.map.memory.mb = 1536
mapreduce.map.java.opts = -Xmx2560m

Слайд 41FAILURE CATEGORY 3 - TOO MANY USERS
Data access control
Inter-departmental resource contention
(too

many jobs)



Слайд 42TOO MANY USERS - QUEUE ACCESS
Use queue ACLs
restrict which users can

submit jobs to a queue
per queue administrator roles:
submit job
administer job
restrict whether users can view applications in another queue

Слайд 43DATA ACCESS CONTROL
By default, Hadoop supports UNIX style file permissions
Easy to

circumvent
HADOOP_USER_NAME=hdfs hdfs dfs -rm /priv/data
Use Kerberos

Слайд 44DATA ACCESS CONTROL - ACCOUNTABILITY




HDFS Audit logs
Produced by NameNode

015-02-24 20:59:45,382 INFO

FSNamesystem.audit: allowed=true ugi=soam (auth:SIMPLE) ip=/10.251.255.181 cmd=delete src=/hive/what_a_con.db dst=/user/soam/.Trash/Current/hive/what_a_con.db perm=soam:hiveusers:rwxrwxr-x

Слайд 45SQUEEZE MORE CAPACITY FROM CLUSTER



Application Layer
Execution Framework
Core Hadoop Layer
Targeted upgrades, optimizations

Слайд 46SQUEEZE MORE CAPACITY FROM CLUSTER
Optimizations:
Application layer:
Query optimizations, algorithmic level optimizations
Upgrading:
Execution Framework:
Tremendous

performance improvements in Hive/Tez, Spark over the past two years
Pig, Cascading all continue to improve
Hadoop layer:
Recent focus on security, stability
Recommendation:
Focus on upgrading execution framework




Слайд 47QUESTIONS? COMMENTS?

Похожие презентации

ВВЕДЕНИЕ ФГОС ОСНОВНОГО ОБЩЕГО ОБРАЗОВАНИЯ МЕХАНИЗМЫ ВВЕДЕНИЯ 213
Требования к оформлению отчётов по практике, курсовых и выпускных квалификационных 276
Лицейское образование в школе. 245
Виктор Маркович Шкловский 391
Қошмұхамбет Дүйсебайұлы Кемеңгеров 519
Масштабируемая система голосования на базе PostgreSQL PgQ 270

Обратная связь

Если не удалось найти и скачать презентацию, Вы можете заказать его на нашем сайте. Мы постараемся найти нужный Вам материал и отправим по электронной почте. Не стесняйтесь обращаться к нам, если у вас возникли вопросы или пожелания:

Email: Нажмите что бы посмотреть 

Что такое ThePresentation.ru?

Это сайт презентаций, докладов, проектов, шаблонов в формате PowerPoint. Мы помогаем школьникам, студентам, учителям, преподавателям хранить и обмениваться учебными материалами с другими пользователями.

Для правообладателей

Яндекс.Метрика