Skip to content

Latest commit

 

History

History
194 lines (129 loc) · 9.41 KB

README.md

File metadata and controls

194 lines (129 loc) · 9.41 KB
Raw

nifi-logo

NiFi

Since version 1.5.0 you can use NiFi Registry service to maintain flow versions.

1.x

  • Version Layers 1.9.0 = 1.9 = latest
  • Version Layers 1.8.0 = 1.8
  • Version Layers 1.7.1 = 1.7
  • Version Layers
  • Version Layers 1.6.0 = 1.6
  • Version Layers 1.5.0 = 1.5
  • Version Layers 1.4.0 = 1.4
  • Version Layers 1.3.0 = 1.3
  • Version Layers 1.2.0 = 1.2
  • Version Layers 1.1.2 = 1.1
  • Version Layers
  • Version Layers
  • Version Layers 1.0.1 = 1.0
  • Version Layers

0.x

  • Version Layers 0.7.4 = 0.7
  • Version Layers
  • Version Layers
  • Version Layers
  • Version Layers
  • Version Layers 0.6.1 = 0.6

Docker image for Apache NiFi.

  • Docker builds Docker Pulls Docker Stars

Created from NiFi base image to minimize traffic and deployment time in case of changes should be applied on top of NiFi

Why base image is required?

DockerHub does not cache image layers while compilation. Thus creation of base image (with pure NiFi) mitigates this issue and let us to experiment/play with NiFi settings w/o downloading full NiFi archive (more than 800MB) each time when we change smth. in configuration (or libs, add-ons, etc.) and recompile docker image. Only our changes will be pulled out from Docker Hub instead of full image.

 ______
< NiFi >
 ------
    \
     \
      \
                    ##        .
              ## ## ##       ==
           ## ## ## ##      ===
       /""""""""""""""""___/ ===
  ~~~ {~~ ~~~~ ~~~ ~~~~ ~~ ~ /  ===- ~~~
       \______ o          __/
        \    \        __/
          \____\______/

Please use corresponding branches from this repo to play with code.

Overview

🔵 Dockerized and parametrized single- and multi-host NiFi.
🔵 Site-to-site communication is switched on.
🔵 Scalability is supported.
🔴 SSL implementation sholud be the next step.

Deployment options:

  • Standalone NiFi node (by default built directly from image)
  • Single-host NiFi cluster (within sigle docker-machine)
  • Multi-host NiFi cluster (within several physical hosts and/or several docker-machines)

Migration from 0.x version

All required information can be found here

Used ports (all of them are configurable)

  • 2883 - 0.x only NiFi Cluster Manager/unicast manager protocol port
  • 2881 - NiFi site to site communication port
  • 2882 - NiFi cluster node protocol port
  • 2181 - Zookeeper client port
  • 2888 - Zookeeper port for monitoring NiFi nodes availability
  • 3888 - Zookeeper port for NiFi Cluster Coordinator election

Exposed ports

  • 8080 - NiFi web application port
  • 8443 - NiFi web application secure port
  • 8081 - NiFi ListenHTTP processor port

!!! Important note !!!

In version 1.5.0 "http request header check" has been implemented on NiFi side. Thus it breaches native Docker functionality with automatic ports assignment. At the moment NiFi web http port and docker port should be equal.

So you can use dockerized NiFi 1.5 in two ways:

  1. Use static Docker port (8080) which equal to default NiFi web http port
docker run -d -p 8080:8080 xemuliam/nifi
  1. Use NIFI_WEB_HTTP_PORT environment variable with value which is equal to Docker port (mentioned environment variable let NiFi to be ran at specified web http port):
docker run -d -p 9999:9999 -e NIFI_WEB_HTTP_PORT=9999 xemuliam/nifi

Volumes

All below volumes can be mounted to docker host machine folders or shared folders to easy maintain data inside them.

NiFi-specific:

  • /opt/nifi/logs
  • /opt/nifi/flowfile_repository
  • /opt/nifi/database_repository
  • /opt/nifi/content_repository
  • /opt/nifi/provenance_repository

User-specific:

  • /opt/datafiles
  • /opt/scriptfiles
  • /opt/certfiles

Additional environment properties

To add more flexibility in configuration there are some environment variables have been added to the image.

  • BANNER_TEXT - NiFi instance banner text to be able to easily recognize instance from first look on UI
  • S2S_PORT - NiFi Site-to-site communication port. If empty, following value will be used: 2881

Official Apache NiFi Documentation and Guides

ListenHTTP Processor

The standard library has a built-in processor for an HTTP endpoint listener. That processor is named ListenHTTP. You should set the Listening Port of the instantiated processor to 8081 if you follow the instructions from above.

Usage

This image can either be used as a image for building on top of NiFi or just to experiment with. I personally have not attempted to use this in a production use case.

Pre-Requisites

Ensure the following pre-requisites are met (due to some blocker bugs in earlier versions). As of today, the latest Docker Toolbox and Homebrew are fine.

  • Docker 1.10+
  • Docker Compose 1.6.1+
  • Docker Machine 0.6.0+

(all downloadable as a single Docker Toolbox package as well)

How to use from Kitematic

  1. Start Kitematic
  2. Enter xemuliam in serach box
  3. Choose nifi image
  4. Click Create button

Kitematic will assign all ports and you'll be able to run NiFi web-interface directly from Kitematic.

How to use from Docker CLI

  1. Start Docker Quickstart Terminal
  2. Run command docker run -d -p 8080:8080 -p 8081:8081 -p 8443:8443 xemuliam/nifi
  3. Check Docker machine IP docker-machine ls
  4. Use IP from previous step in address bar of your favorite browser, e.g. http://192.168.99.100:8080/nifi

How to use NiFi in cluster mode

Please read explanation.

Enjoy! :)