📋
Flink on Zeppelin
  • Setup Zeppelin
  • Main Features
  • Flink on Zeppelin Architecture
  • Execution mode
    • local mode
    • remote mode
    • yarn mode
    • yarn-application mode
  • Languages
    • Scala
    • PyFlink
    • SQL
  • Hive Integration
  • Interpreter binding mode
  • Configure Flink Interpreter
  • Third party dependencies
  • UDF
  • Checkpoint & Savepoint
  • Recovery
  • Flink Sql Cookbook
  • FAQ
Powered by GitBook
On this page
  • Shared Mode
  • Isolated Per User
  • Isolated Per Note (Recommended)
  • Community

Was this helpful?

Interpreter binding mode

PreviousHive IntegrationNextConfigure Flink Interpreter

Last updated 3 years ago

Was this helpful?

Interpreter binding mode means the relationship between note and interpreter process. In the chapter of Zeppelin architecture, we learned that one Zeppelin instance can launch several flink interpreters. So in which interpreter process does your job run, it depends on the interpreter binding mode.

Here we would talk about 3 interpreter binding modes.

  • Shared Mode

  • Isolated Per User Mode

  • Isolated Per Note Mode

Shared Mode

Shared mode is the default mode, which means all the notes / all the users share the same flink interpreter. So that means all the flink jobs will be submitted to the same flink cluster.

Isolated Per User

Isolated Per Note (Recommended)

Isolated Per Note means each note has its own flink Interpreter. That means each note is isolated. This is usually the recommended approach.

Community

Join Zeppelin community to discuss with others

Isolated per user means every user has its own flink interpreter. ( This only works when you in Zeppelin)

enable shiro
Community
Logo