This documentation is for an out-of-date version of Apache Flink. We recommend you use the latest stable version.
Important: Maven artifacts which depend on Scala are now suffixed with the Scala major version, e.g. "2.10" or "2.11". Please consult the migration guide on the project Wiki.

Local Setup

This documentation is intended to provide instructions on how to run Flink locally on a single machine.


Go to the downloads page and get the ready to run package. If you want to interact with Hadoop (e.g. HDFS or HBase), make sure to pick the Flink package matching your Hadoop version. When in doubt or you plan to just work with the local file system pick the package for Hadoop 1.2.x.

Back to top


Flink runs on Linux, Mac OS X and Windows. The only requirement for a local setup is Java 1.7.x or higher. The following manual assumes a UNIX-like environment, for Windows see Flink on Windows.

You can check the correct installation of Java by issuing the following command:

java -version

The command should output something comparable to the following:

java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

Back to top


For local mode Flink is ready to go out of the box and you don’t need to change the default configuration.

The out of the box configuration will use your default Java installation. You can manually set the environment variable JAVA_HOME or the configuration key in conf/flink-conf.yaml if you want to manually override the Java runtime to use. Consult the configuration page for further details about configuring Flink.

Back to top

You are now ready to start Flink. Unpack the downloaded archive and change to the newly created flink directory. There you can start Flink in local mode:

$ tar xzf flink-*.tgz
$ cd flink
$ bin/
Starting job manager

You can check that the system is running by checking the log files in the logs directory:

$ tail log/flink-*-jobmanager-*.log
INFO ... - Initializing memory manager with 409 megabytes of memory
INFO ... - Trying to load org.apache.flinknephele.jobmanager.scheduler.local.LocalScheduler as scheduler
INFO ... - Setting up web info server, using web-root directory ...
INFO ... - Web info server will display information about nephele job-manager on localhost, port 8081.
INFO ... - Starting web info server for JobManager on port 8081

The JobManager will also start a web frontend on port 8081, which you can check with your browser at http://localhost:8081.

Back to top

If you want to run Flink on Windows you need to download, unpack and configure the Flink archive as mentioned above. After that you can either use the Windows Batch file (.bat) or use Cygwin to run the Flink Jobmanager.

Starting with Windows Batch Files

To start Flink in local mode from the Windows Batch, open the command window, navigate to the bin/ directory of Flink and run start-local.bat.

Note: The bin folder of your Java Runtime Environment must be included in Window’s %PATH% variable. Follow this guide to add Java to the %PATH% variable.

$ cd flink
$ cd bin
$ start-local.bat
Starting Flink job manager. Webinterface by default on http://localhost:8081/.
Do not close this batch window. Stop job manager by pressing Ctrl+C.

After that, you need to open a second terminal to run jobs using flink.bat.

Back to top

Starting with Cygwin and Unix Scripts

With Cygwin you need to start the Cygwin Terminal, navigate to your Flink directory and run the script:

$ cd flink
$ bin/
Starting Nephele job manager

Back to top

If you are installing Flink from the git repository and you are using the Windows git shell, Cygwin can produce a failure similiar to this one:

c:/flink/bin/ line 30: $'\r': command not found

This error occurs, because git is automatically transforming UNIX line endings to Windows style line endings when running in Windows. The problem is, that Cygwin can only deal with UNIX style line endings. The solution is to adjust the Cygwin settings to deal with the correct line endings by following these three steps:

  1. Start a Cygwin shell.

  2. Determine your home directory by entering

cd; pwd

It will return a path under the Cygwin root path.

  1. Using NotePad, WordPad or a different text editor open the file .bash_profile in the home directory and append the following: (If the file does not exist you have to create it)
set -o igncr

Save the file and open a new bash shell.

Back to top