This version is outdated by a newer approved version.DiffThis version (2023/05/11 08:42) was approved by katrin.The Previously approved version (2023/05/10 13:11) is available.Diff

This is an old revision of the document!

Big Data

VSC-4 has Big Data modules for running

  • MapReduce jobs
    • in several programming languages, including Java, and
    • using executables which can stream data from standard input to standard output (e.g. grep, cut, tr, sed, …), and
  • Spark jobs using
    • Python,
    • Java,
    • Scala,
    • R,
    • SQL

either on standard file systems (using Spectrum Scale, formerly GPFS) or HDFS (Hadoop distributed file system) locally on the nodes of a job.

Big Data and HPC

Among the advantages of Big Data also on HPC environments like VSC, we want to mention

  • very easy coding, in many languages, including data centric ones like R or SQL,
  • automatic parallelization without any changes in the user program, and
  • extremely good scaling behaviour.

Users have to be aware of difficulties for running Big Data jobs on HPC clusters, namely of shared resources and granularity.

  • File systems are shared by all users. Users with high file system demand should use the local HDFS, if the same data is read more than once in a job. Please, do not submit many Big Data jobs at the same time, e.g. slurm array jobs!
  • Login nodes and internet connections are shared by all users. Bringing huge amounts of data to VSC takes some time. Please make sure that other users of VSC are not affected! (One or two ssh-connections from your workstation are OK, whereas 10 simultaneous connections from a computer with high internet bandwidth, i.e. at least 10Mb/s, could affect others.)
  • Only very coarse grained parallelization will work with Big Data frameworks. Typically parallelization is done by partitioning input data (automatically) and doing the majority of the calculation independently by separated processes.

In the context of high performance computing a typical application of Big Data methods is pre- and/or postprocessing of large amounts of data, e.g.

  • filtering,
  • data cleaning,
  • discarding input fields which are not required,
  • counting,
  • …

Frameworks and applications using Big Data methods are shared among many scientific communities.

Apache Spark on VSC

There are many frameworks in Data Science that are using <html><span style=“color:#cc3300;font-size:100%;”>&dzigrarr;</span> </html> Apache Spark<html>TM</html> , for instance, ADAM for genomic analysis, GeoTrellis for geospatial data analysis, or Koalas (distributed Pandas).

Example slurm & python scripts

Let us calculate the value of pi by means of the following Python script pi.py (example originally taken from the Spark distribution): 

from operator import add
from random import random
import sys
 
from pyspark.sql import SparkSession
 
if __name__ == "__main__":
    """
        Usage: pi [partitions]
    """
    spark = SparkSession\
        .builder\
        .appName("PythonPi")\
        .getOrCreate()
 
    partitions = int(sys.argv[1]) if len(sys.argv) > 1 else 2
    n = 100000 * partitions
 
    def f(_):
        x = random() * 2 - 1
        y = random() * 2 - 1
        return 1 if x ** 2 + y ** 2 <= 1 else 0
 
    count = spark.sparkContext\
        .parallelize(range(1, n + 1), partitions)\
        .map(f)\
        .reduce(add)
    pi = 4.0 * count / n
    print(f"Pi is roughly {pi}")
 
    spark.stop()

The idea of the calculation is to check (very often) whether a random point in the area [-1,-1; 1,1] is within a unit circle (i.e. has a distance less than 1 from origin). Since we know formulas for the area of the square as well as the circle we can estimate pi.

Assuming that the script is saved to $HOME/pi.py' we can use the following SLURM script pi.slrm to run the code on VSC-4: 

#!/bin/bash
#SBATCH --nodes=1
#SBATCH --job-name=spark-yarn-pi
#SBATCH --time=00:10:00
#SBATCH --error=err_spark-yarn-pi-%A
#SBATCH --output=out_spark-yarn-pi-%A
#SBATCH --partition=skylake_0096
#SBATCH --qos=skylake_0096
 
module purge
 
# you can choose one of the following python versions
# with the current hadoop/spark installation on VSC-4
# note: the current hadoop version does NOT work with python 3.11
module load python/3.10.7-gcc-12.2.0-5a2kkeu
# module load python/3.9.13-gcc-12.2.0-ctxezzj
# module load python/3.8.12-gcc-12.2.0-tr7w5qy
 
module load openjdk
module load hadoop
module load spark
 
export PDSH_RCMD_TYPE=ssh
 
prolog_create_key.sh
. vsc_start_hadoop.sh
. vsc_start_spark.sh
 
spark-submit --master yarn --deploy-mode client --num-executors 140 \
      --executor-memory 2G $HOME/pi.py 1000
 
. vsc_stop_spark.sh
. vsc_stop_hadoop.sh
 
epilog_discard_key.sh

In this slurm script we have

  • slurm commands, starting with #SBATCH to set the job name, the maximum execution time and where the output files will go, as well as the slurm qos and partition that should be used,
  • module commands, loading all the modules which are required by our job: python, Java (Hadoop is written in Java), Hadoop, and Spark,
  • setup scripts which create temporary ssh keys, and start Hadoop and Spark services in user context on the nodes of the job,
  • commands to start our job with 'spark-submit', and
  • a script to discard the temporary ssh keys.

The script is submitted to the slurm scheduler by executing: 

$ sbatch pi.slrm

MapReduce: Concepts and example

MapReduce splits work into the phases

  • map: a subset of the input data is processed by a single process, e.g. filtering,
  • shuffle: sort the output of the map phase by its key,
  • reduce: combine the sorted data

An example is 

#!/bin/bash
#SBATCH --job-name=simple_mapreduce
#SBATCH --nodes=1 --time=00:10:00
#SBATCH --error=simple_mapreduce_err
#SBATCH --output=simple_mapreduce_out
 
module purge
module load openjdk/11.0.2-gcc-9.1.0-ayy5f5t
module load hadoop
 
prolog_create_key.sh
. vsc_start_hadoop.sh
 
hdfs dfs -mkdir input
hdfs dfs -put data/wiki\_sample\_2400lines input/
hdfs dfs -rm -r tmp_out
 
mapred streaming -D mapreduce.job.maps=4 -input input/wiki_sample_2400lines \
    -output tmp_out -mapper /bin/cat -reducer '/bin/wc -l'
 
# check output in simple_mapreduce_out and simple_mapreduce_err
# check job output on HDFS
hdfs dfs -ls tmp_out
echo "The number of lines is:"
hdfs dfs -cat tmp_out/part-*
 
epilog_discard_key.sh

Further examples

For examples in Scala, R, and SQL, including slurm scripts to run on VSC, we want to refer to the course material in Big Data on VSC.

Available modules

To use Big Data on VSC use those modules:

  • python/3.8.0-gcc-9.1.0-wkjbtaa
  • openjdk/11.0.2-gcc-9.1.0-ayy5f5t
  • hadoop
  • spark
  • r

Depending on the application, choose the right combination:

  • MapReduce ⇒ openjdk + hadoop
  • Scala ⇒ openjdk + hadoop + spark
  • Java ⇒ openjdk + hadoop + spark
  • PySpark ⇒ openjdk + hadoop + spark + python
  • R ⇒ openjdk + hadoop + spark + r

Background

What is VSC actually doing to run a Big Data job using Hadoop and/or Spark?

HPC

User jobs on VSC are submitted using Slurm, thus making sure that a job gets a well defined execution environment which is similar in terms of resources and performance for each similar job execution.

Big Data

Big Data jobs on the other hand are often executed on Big Data clusters, which make sure that

  • programs are started on the nodes where data is stored, thus reducing communication overhead,
  • load balancing is done automatically,
  • fault tolerance is added by the framework,
  • very good scaling behaviour is ensured without any changes in user programs.

Much of this work is done by Yarn (Yet another resource negotiator), which is a scheduler (and runs usually at a similar level on Big Data clusters as Slurm is running on VSC).

Combination of HPC and Big Data

In our setup on VSC we combine those two worlds of HPC and Big data by starting Yarn, HDFS and spark in user context within a job (on the nodes belonging to the job). User data can be accessed

  • from the standard VSC paths using Spectrum Scale (formerly GPFS), or
  • from HDFS, which is started locally on the local SSDs of the compute nodes. In this case the data has to be copied in and/or out at the beginning/end of the job. After a job run, the local HDFS instance is destroyed and remaining data is lost.

VSC has several scripts - most are optional - which are added to the path using 'module load hadoop' and 'module load spark':

  • prolog_create_key.sh and epilog_discard_key.sh, which are required to start services on other nodes, but also to access the local (master) node.
  • vsc_start_hadoop.sh, which starts Yarn (scheduler) and HDFS (distributed file system) on the nodes of the job. (If only one node is used this is optional, since Spark can also run with its own scheduler and without HDFS.)
  • vsc_start_spark.sh, which starts the Spark service on the nodes of the job. (This is optional, since MapReduce jobs run without Spark.)
  • vsc_stop_hadoop.sh, which is usually not required since the services are stopped at the end by the system anyway.
  • vsc_stop_spark.sh, which is usually not required since the services are stopped at the end by the system anyway.

References

Hadoop at the TU Wien

At the Technische Universität Wien there is a Big Data cluster, mainly for teaching purposes, which is also used by researchers.

  • doku/bigdata.1683794730.txt.gz
  • Last modified: 2024/10/24 10:21
  • (external edit)