Skip to main content

Leveraging YARN to provision java apps on Cloud


Over the last few days, we have heard quite a bit of press on Hadoop Yarn. Let us continue the beat and learn a unique PAAS architecture on Hadoop Yarn.

In an article, Jaigak Song describes his idea and prototype done as part of research at SAP Labs. The source code is available at github.

The prototype has been created to provision Java applications on a PAAS environment, and start, stop their instances as required.

The following projects are included as part of source code:
PAAS Client (PaasClient)
PaasClient is a dedicated YARN client that works like a command shell to process PAAS commands…

PAAS Application Master (PaaSAppMaster)
PaasAppMaster is a YARN application master that manages a lifecycle of PAAS application instances…

PAAS Application Container (PaasAppContainer) – Jetty Web Container
PaasAppContainer is instantiated by PaasAppMaster as a YARN container according to the requested resource limit…”

 
           this.execCommand(session, "hadoop fs -rm /PAAS/" + fileName);
this.execCommand(session, String.format("hadoop fs -put ~/i827616/%s /PAAS/%s", fileName, fileName));
 
· An Admin user issues a push command in PaasClient like “push /Users/PAAS/svcA.war”, where svcA.war file is a web application file of the service named ‘svcA’. Then the PaasClient uploads the file to the Hadoop server by using ‘scp’ and ‘ssh’. There is a dedicated directory in the Hadoop file system to save War files (e.g. /PAAS/), while non-application libraries and jar files are stored in a different directory.”

Source code snapshot (click on file names to view source) :
HadoopPaas / PaasZooClient / src / com / sap / zookeeper
HadoopPaas / PaasClient / src / com / sap / hadoop / paas
HadoopPaas / PaasAppMaster / src / com / sap / hadoop / master
HadoopPaas / PaasAppContainer / src / com / sap / hadoop / client


A interesting prototype for sure, read the article and contribute to code for further cool projects on the concept.

Comments

Popular posts from this blog

In-memory data model with Apache Gora

Open source in-memory data model and persistence for big data framework Apache Gora™ version 0.3, was released in May 2013. The 0.3 release offers significant improvements and changes to a number of modules including a number of bug fixes. However, what may be of significant interest to the DynamoDB community will be the addition of a gora-dynamodb datastore for mapping and persisting objects to Amazon's DynamoDB. Additionally the release includes various improvements to the gora-core and gora-cassandra modules as well as a new Web Services API implementation which enables users to extend Gora to any cloud storage platform of their choice. This 2-part post provides commentary on all of the above and a whole lot more, expanding to cover where Gora fits in within the NoSQL and Big Data space, the development challenges and features which have been baked into Gora 0.3 and finally what we have on the road map for the 0.4 development drive.
Introducing Apache Gora Although there are var…

Data deduplication tactics with HDFS and MapReduce

As the amount of data continues to grow exponentially, there has been increased focus on stored data reduction methods. Data compression, single instance store and data deduplication are among the common techniques employed for stored data reduction.
Deduplication often refers to elimination of redundant subfiles (also known as chunks, blocks, or extents). Unlike compression, data is not changed and eliminates storage capacity for identical data. Data deduplication offers significant advantage in terms of reduction in storage, network bandwidth and promises increased scalability.
From a simplistic use case perspective, we can see application in removing duplicates in Call Detail Record (CDR) for a Telecom carrier. Similarly, we may apply the technique to optimize on network traffic carrying the same data packets.
Some of the common methods for data deduplication in storage architecture include hashing, binary comparison and delta differencing. In this post, we focus on how MapReduce and…

Pricing models for Hadoop products

A look at the various pricing models adopted by the vendors in the Hadoop ecosystem. While the pricing models are evolving in this rapid and dynamic market, listed below are some of the major variations utilized by companies in the sphere.
1) Per Node:Among the most common model, the node based pricing mechanism utilizes customized rules for determining pricing per node. This may be as straight forward as pricing per name node and data node or could have complex variants of pricing based on number of core processors utilized by the nodes in the cluster or per user license in case of applications.
2) Per TB:The data based pricing mechanism charges customer for license cost per TB of data. This model usually accounts non replicated data for computation of cost.
3) Subscription Support cost only:In this model, the vendor prefers to give away software for free but charges the customer for subscription support on a specified number of nodes. The support timings and level of support further …