hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qi Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1021) Yarn Scheduler Load Simulator
Date Sun, 02 Mar 2014 22:03:25 GMT

    [ https://issues.apache.org/jira/browse/YARN-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917585#comment-13917585
] 

Qi Zhang commented on YARN-1021:
--------------------------------

Hi @Wei Yan. I am trying to use SLS but always meet with the following exception. Can you
tell me what is the reason? Thank you!

-bash-3.2$ sudo sh share/hadoop/tools/sls/bin/slsrun.sh --input-rumen=share/hadoop/tools/sls/sample-data/2jobs2min-rumen-jh.json
--output-dir=share/hadoop/tools/sls/sample_output
log4j:WARN No appenders could be found for logger (org.apache.hadoop.util.Shell).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /usr/local/hadoop-2.3.0/lib/native/libhadoop.so.1.0.0
which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link
it with '-z noexecstack'.
java.lang.NullPointerException
	at org.apache.hadoop.yarn.sls.web.SLSWebApp.<init>(SLSWebApp.java:82)
	at org.apache.hadoop.yarn.sls.scheduler.ResourceSchedulerWrapper.initMetrics(ResourceSchedulerWrapper.java:463)
	at org.apache.hadoop.yarn.sls.scheduler.ResourceSchedulerWrapper.setConf(ResourceSchedulerWrapper.java:162)
	at org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:73)
	at org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:133)
	at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.createScheduler(ResourceManager.java:230)
	at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$RMActiveServices.serviceInit(ResourceManager.java:355)
	at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
	at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.createAndInitActiveServices(ResourceManager.java:775)
	at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.serviceInit(ResourceManager.java:197)
	at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
	at org.apache.hadoop.yarn.sls.SLSRunner.startRM(SLSRunner.java:163)
	at org.apache.hadoop.yarn.sls.SLSRunner.start(SLSRunner.java:137)
	at org.apache.hadoop.yarn.sls.SLSRunner.main(SLSRunner.java:524)
Exception in thread "pool-2-thread-72" java.lang.NullPointerException
	at org.apache.hadoop.yarn.sls.scheduler.ResourceSchedulerWrapper.addAMRuntime(ResourceSchedulerWrapper.java:721)
	at org.apache.hadoop.yarn.sls.appmaster.AMSimulator.lastStep(AMSimulator.java:196)
	at org.apache.hadoop.yarn.sls.appmaster.MRAMSimulator.lastStep(MRAMSimulator.java:390)
	at org.apache.hadoop.yarn.sls.scheduler.TaskRunner$Task.run(TaskRunner.java:94)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)
Exception in thread "pool-2-thread-98" java.lang.NullPointerException
	at org.apache.hadoop.yarn.sls.scheduler.ResourceSchedulerWrapper.addAMRuntime(ResourceSchedulerWrapper.java:721)
	at org.apache.hadoop.yarn.sls.appmaster.AMSimulator.lastStep(AMSimulator.java:196)
	at org.apache.hadoop.yarn.sls.appmaster.MRAMSimulator.lastStep(MRAMSimulator.java:390)
	at org.apache.hadoop.yarn.sls.scheduler.TaskRunner$Task.run(TaskRunner.java:94)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)

> Yarn Scheduler Load Simulator
> -----------------------------
>
>                 Key: YARN-1021
>                 URL: https://issues.apache.org/jira/browse/YARN-1021
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: scheduler
>            Reporter: Wei Yan
>            Assignee: Wei Yan
>             Fix For: 2.3.0
>
>         Attachments: YARN-1021-demo.tar.gz, YARN-1021-images.tar.gz, YARN-1021.patch,
YARN-1021.patch, YARN-1021.patch, YARN-1021.patch, YARN-1021.patch, YARN-1021.patch, YARN-1021.patch,
YARN-1021.patch, YARN-1021.patch, YARN-1021.patch, YARN-1021.patch, YARN-1021.patch, YARN-1021.patch,
YARN-1021.patch, YARN-1021.patch, YARN-1021.pdf
>
>
> The Yarn Scheduler is a fertile area of interest with different implementations, e.g.,
Fifo, Capacity and Fair  schedulers. Meanwhile, several optimizations are also made to improve
scheduler performance for different scenarios and workload. Each scheduler algorithm has its
own set of features, and drives scheduling decisions by many factors, such as fairness, capacity
guarantee, resource availability, etc. It is very important to evaluate a scheduler algorithm
very well before we deploy it in a production cluster. Unfortunately, currently it is non-trivial
to evaluate a scheduling algorithm. Evaluating in a real cluster is always time and cost consuming,
and it is also very hard to find a large-enough cluster. Hence, a simulator which can predict
how well a scheduler algorithm for some specific workload would be quite useful.
> We want to build a Scheduler Load Simulator to simulate large-scale Yarn clusters and
application loads in a single machine. This would be invaluable in furthering Yarn by providing
a tool for researchers and developers to prototype new scheduler features and predict their
behavior and performance with reasonable amount of confidence, there-by aiding rapid innovation.
> The simulator will exercise the real Yarn ResourceManager removing the network factor
by simulating NodeManagers and ApplicationMasters via handling and dispatching NM/AMs heartbeat
events from within the same JVM.
> To keep tracking of scheduler behavior and performance, a scheduler wrapper will wrap
the real scheduler.
> The simulator will produce real time metrics while executing, including:
> * Resource usages for whole cluster and each queue, which can be utilized to configure
cluster and queue's capacity.
> * The detailed application execution trace (recorded in relation to simulated time),
which can be analyzed to understand/validate the  scheduler behavior (individual jobs turn
around time, throughput, fairness, capacity guarantee, etc).
> * Several key metrics of scheduler algorithm, such as time cost of each scheduler operation
(allocate, handle, etc), which can be utilized by Hadoop developers to find the code spots
and scalability limits.
> The simulator will provide real time charts showing the behavior of the scheduler and
its performance.
> A short demo is available http://www.youtube.com/watch?v=6thLi8q0qLE, showing how to
use simulator to simulate Fair Scheduler and Capacity Scheduler.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message