How to use Drill to parse ResourceManager Rest API results

How to use Drill to parse ResourceManager Rest API results

rs:http://www.openkb.info/search/label/drill

Goal:

ResourceManager REST API provides all detailed information regarding YARN applications, metrics of YARN cluster, etc.
This article provides a simple demo on how to use Drill to query the result of the REST APIs.
One example use case is to show the largest YARN applications which are currently running.

Env:

Drill 1.8
Hadoop 2.7.0

Solution:

1. Save the current output of RM REST API as a json file on MFS(or HDFS).

1
curl -v -X GET -H "Content-Type: application/json" http://s1.poc.com:8088/ws/v1/cluster/apps > /mapr/mysuper.cluster.com/tmp/restapi/data.json
Here "s1.poc.com" is the RM node.

2. Use Drill to parse the json file to answer the question Cluster Admin want to ask.

For example, to show the largest YARN applications which are currently running:
1
2
3
4
5
6
7
with tmp as
(
select flatten(t.apps.app) as col from dfs.tmp.`restapi/data.json` t
)
select tmp.col.id,tmp.col.`user` as `user`,tmp.col.runningContainers as `runningContainers`,tmp.col.allocatedMB as `allocatedMB`,tmp.col.allocatedVCores as `allocatedVCores` from tmp
where tmp.col.state='RUNNING'
order by tmp.col.runningContainers desc;
The result is:
1
2
3
4
5
6
7
+---------------------------------+-------+--------------------+--------------+------------------+
|             EXPR$0              | user  | runningContainers  | allocatedMB  | allocatedVCores  |
+---------------------------------+-------+--------------------+--------------+------------------+
| application_1475192050844_0003  | mapr  | 4                  | 16384        | 4                |
| application_1475192050844_0004  | mapr  | 1                  | 2048         | 1                |
+---------------------------------+-------+--------------------+--------------+------------------+
2 rows selected (0.525 seconds)

Commentaires

Enregistrer un commentaire

Posts les plus consultés de ce blog

Controlling Parallelism in Spark by controlling the input partitions by controlling the input partitions

Image
It is useful to be able to control the degree of parallelism when using Spark. Spark provides a very convenient method to increase the degree of parallelism which should be adequate in practice. This blog entry of the "Inside Spark" series describes the knobs Spark uses to control the degree of parallelism. Controlling the number of partitions in the " local " mode Spark is designed ground up to enable unit testing. To control the degree of parallelism in the local mode simply utilize the function JavaRDD<String> org.apache.spark.api.java.JavaSparkContext.parallelize(List<String> list, int numSlices) The following snippet of code demonstrates this usage- public class SparkControlPartitionSizeLocally { public static void main ( String [] args ) { JavaSparkContext sc = new JavaSparkContext ( "local" , "localpartitionsizecontrol" ); String input = "four score and sev
Lire la suite

Spark performance optimization: shuffle tuning

Image
Article directory 1 shuffle tuning 1.1 Summary of tuning 1.2 Overview of ShuffleManager Development 1.3 HashShuffleManager operating principle 1.3.1 Unoptured HashShuffleManager 1.3.2 Optimized HashShuffleManager 1.4 SortShuffleManager operating principle 1.4.1 General operating mechanism 1.4.2 bypass running mechanism 1.5 shuffle related parameters tuning 1.5.1 spark.shuffle.file.buffer 1.5.2 spark.reducer.maxSizeInFlight 1.5.3 spark.shuffle.io.maxRetries 1.5.4 spark.shuffle.io.retryWait 1.5.5 spark.shuffle.memoryFraction 1.5.6 spark.shuffle.manager 1.5.7 spark.shuffle.sort.bypassMergeThreshold 1.5.8 spark.shuffle.consolidateFiles 2 write in the last words Shuffle Summary of tuning Most of the performance of Spark operations is mainly consumed in the shuffle link, because the link contains a large number of disk IO, serialization, network data transmission and othe
Lire la suite

Spark optimization

Image
One operation and maintenance 1. Master hang up, standby restart is also invalid Master defaults to 512M of memory, when the task in the cluster is particularly high, it will hang, because the master will read each task event log log to generate spark ui, the memory will naturally OOM, you can run the log See that the master of the start through the HA will naturally fail for this reason. solve Increase the Master's memory spark-env.sh , set in the master node spark-env.sh : export SPARK_DAEMON_MEMORY 10g # 根据你的实际情况 Reduce the job information stored in the Master memory spark.ui.retainedJobs 500 # 默认都是1000 spark.ui.retainedStages 500 Hang up or suspend Sometimes we will see the web node in the web ui disappear or in the dead state, the task of running the node will report a variety of lost worker errors, causing the same reasons and the above, worker memory to save a lot of ui The information leads to gc when the heartbeat is lost
Lire la suite