What are the major components of the Aneka MapReduce Programming Model?

-

ANEKA MAPREDUCE PROGRAMMING

Aneka follows the reference model published by Google and implemented by Hadoop to give an implementation of the MapReduce abstractions. The MapReduce Programming Model specifies the abstractions and runtime support required to build MapReduce applications on top of Aneka. For MapReduce programming using Aneka, you have to have a basic understanding of object-oriented programming, cloud computing, distributed systems, and a good understanding of the .NET framework and C#. Similarly, Microsoft Visual Studio with C# and Aneka also need to be installed.

MapReduce.NET is a MapReduce solution for data centers that is similar to Google's MapReduce but focuses on the.NET and Windows platforms. MapReduce.NET offers a set of storage APIs to wrap input key/value pairs into starting files and extract result key/value pairs from results files, as well as an object. oriented interface for programming maps and reducing functions.

MapReduce.NET is based on master-slave architecture. 

Its main components include a manager, scheduler, executor, and storage.

1. Manager: The manager acts as a MapReduce computation agent. It sends the application to the MapReduce scheduler and gathers the final results after the execution is complete.

2. Schedular: The schedular assigns subtask to available resources when a user submits MapReduce.NET applications to it. During execution, it checks the progress of each job and performs task migration operations if certain nodes are ch slower than others owing to heterogeneity.

3. Executor: Each executor awaits a task execution order from the scheduler. Normally, the input data for a Map job is located locally. Otherwise, the executor will have to collect input data from neighbors. Before executing a Reduce job, the executor must get all of the input and combine it. Furthermore, the executor checks the progress of the task execution and sends the status to the scheduler regularly.

4. Storage: The storage component of MapReduce .NET provides a distributed storage service over the .NET platform. It arranges disk spaces on all available resources as a virtual storage pool and provides an object-based interface with a flat namespace for managing data stored in it.

Figure 5.24 depicts an example MapReduce.NET deployment with Aneka setup. Client processes simply include the libraries necessary to connect to Aneka and submit MapReduce tasks for execution. Typical management will be ahead of the MapReduce schedular installed on the schedular node and the MapReduce executor deployed on the executor node. Using the Windows Shared File Services, each executor node will access shared among all MapReduce execution.

Comments

Post a Comment

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

-
Image
a) A Snowflake Shema is shown in figure below: b) The specific OLAP operations to be performed: 1. Roll-up on course from course_id to department. 2. Roll-up on a student from student_id to university. 3. Dice on course, student with department ="CS" and university = "biguniversity" 4. Drill-down on a student from the university to student_name. c) N = 4 dimensions The cube will contain 54 = 625 cuboids.
Read more

Describe how cloud computing technology can be applied to support remote ECG monitoring.

-
Image
  Healthcare: ECG (Electrocardiogram) Analysis in cloud computing Healthcare is a field, subject, sector, or territory in which information technology has several uses. These apps are being used to aid businesses in supporting scientists in developing disease prevention solutions. Cloud computing has emerged as an appealing alternative for constructing health monitoring systems as a result of the development of the Internet or to put it another way, as a result of the availability of the internet. The ECG machine, for example, is a health monitoring device that measures the human body's heartbeat and prints the results on graph paper. The electrocardiogram (ECG) measures the electrical activity of the heart's Cardium. A waveform is created as a result of this action, which is repeated throughout time and symbolizes the heartbeat.  The analysis of the shape is used to identify arrhythmias, and it is the most common way of detecting heart diseases. Here the meaning of arrhythmias
Read more

Explain market-Oriented Cloud computing architecture.

-
Image
  Market Oriented Cloud Computing (Mocc) As customers rely on Cloud providers to cover all of their computing needs, they will expect certain Qe from their providers to fulfill their objectives and continue their operations. Cloud providers must examine and satisfy the various QoS standards of each unique consumer as stipulated in unique SLAs. To do this, cloud providers cannot continue to install traditional system-centric resource management architectures that do not give incentives for them to share their resources while still treating all service requests as equal insignificance. Instead, market-oriented resource management is required to maintain the supply and demand for Cloud resources at market equilibrium, provide feedback in the form of economic incentives for both Cloud consumers and providers, and promote QoS-based resource allocation mechanisms that differentiate service requests based on their utility. The diagram depicts a high-level architecture for enabling market-orie
Read more