基础配置

#==============================================================================
# Common
#============================================================================== # The external address of the host on which the JobManager runs and can be
# reached by the TaskManagers and any clients which want to connect. This setting
# is only used in Standalone mode and may be overwritten on the JobManager side
# by specifying the --host <hostname> parameter of the bin/jobmanager.sh executable.
# In high availability mode, if you use the bin/start-cluster.sh script and setup
# the conf/masters file, this will be taken care of automatically. Yarn/Mesos
# automatically configure the host name based on the hostname of the node where the
# JobManager runs. # JobManager的IP地址
jobmanager.rpc.address: localhost # The RPC port where the JobManager is reachable.
#JobManager的RPC端口号
jobmanager.rpc.port: 6123 # The heap size for the JobManager JVM
jobmanager.heap.size: 1024m # The total process memory size for the TaskManager.
#
# Note this accounts for all memory usage within the TaskManager process, including JVM metaspace and other overhead. taskmanager.memory.process.size: 1568m # To exclude JVM metaspace and overhead, please, use total Flink memory size instead of 'taskmanager.memory.process.size'.
# It is not recommended to set both 'taskmanager.memory.process.size' and Flink memory.
#
# taskmanager.memory.flink.size: 1280m # The number of task slots that each TaskManager offers. Each slot runs one parallel pipeline. taskmanager.numberOfTaskSlots: 4 # The parallelism used for programs that did not specify and other parallelism. parallelism.default: 1 # The default file system scheme and authority.
#
# By default file paths without scheme are interpreted relative to the local
# root file system 'file:///'. Use this to override the default and interpret
# relative paths relative to a different file system,
# for example 'hdfs://mynamenode:12345'
#
# fs.default-scheme

高可用部分


#==============================================================================
# High Availability
#============================================================================== # The high-availability mode. Possible options are 'NONE' or 'zookeeper'.
#
# high-availability: zookeeper # The path where metadata for master recovery is persisted. While ZooKeeper stores
# the small ground truth for checkpoint and leader election, this location stores
# the larger objects, like persisted dataflow graphs.
#
# Must be a durable file system that is accessible from all nodes
# (like HDFS, S3, Ceph, nfs, ...)
#
# high-availability.storageDir: hdfs:///flink/ha/ # The list of ZooKeeper quorum peers that coordinate the high-availability
# setup. This must be a list of the form:
# "host1:clientPort,host2:clientPort,..." (default clientPort: 2181)
#
# high-availability.zookeeper.quorum: localhost:2181 # ACL options are based on https://zookeeper.apache.org/doc/r3.1.2/zookeeperProgrammers.html#sc_BuiltinACLSchemes
# It can be either "creator" (ZOO_CREATE_ALL_ACL) or "open" (ZOO_OPEN_ACL_UNSAFE)
# The default value is "open" and it can be changed to "creator" if ZK security is enabled
#
# high-availability.zookeeper.client.acl: open

容错和检查点配置


#==============================================================================
# Fault tolerance and checkpointing
#============================================================================== # The backend that will be used to store operator state checkpoints if
# checkpointing is enabled.
#
# Supported backends are 'jobmanager', 'filesystem', 'rocksdb', or the
# <class-name-of-factory>.
#
# state.backend: filesystem # Directory for checkpoints filesystem, when using any of the default bundled
# state backends.
#
# state.checkpoints.dir: hdfs://namenode-host:port/flink-checkpoints # Default target directory for savepoints, optional.
#
# state.savepoints.dir: hdfs://namenode-host:port/flink-checkpoints # Flag to enable/disable incremental checkpoints for backends that
# support incremental checkpoints (like the RocksDB state backend).
#
# state.backend.incremental: false # The failover strategy, i.e., how the job computation recovers from task failures.
# Only restart tasks that may have been affected by the task failure, which typically includes
# downstream tasks and potentially upstream tasks if their produced data is no longer available for consumption. jobmanager.execution.failover-strategy: region #==============================================================================
# Rest & web frontend
#============================================================================== # The port to which the REST client connects to. If rest.bind-port has
# not been specified, then the server will bind to this port as well.
#
#rest.port: 8081 # The address to which the REST client will connect to
#
#rest.address: 0.0.0.0 # Port range for the REST and web server to bind to.
#
#rest.bind-port: 8080-8090 # The address that the REST & web server binds to
#
#rest.bind-address: 0.0.0.0 # Flag to specify whether job submission is enabled from the web-based
# runtime monitor. Uncomment to disable. #web.submit.enable: false #==============================================================================
# Advanced
#============================================================================== # Override the directories for temporary files. If not specified, the
# system-specific Java temporary directory (java.io.tmpdir property) is taken.
#
# For framework setups on Yarn or Mesos, Flink will automatically pick up the
# containers' temp directories without any need for configuration.
#
# Add a delimited list for multiple directories, using the system directory
# delimiter (colon ':' on unix) or a comma, e.g.:
# /data1/tmp:/data2/tmp:/data3/tmp
#
# Note: Each directory entry is read from and written to by a different I/O
# thread. You can include the same directory multiple times in order to create
# multiple I/O threads against that directory. This is for example relevant for
# high-throughput RAIDs.
#
# io.tmp.dirs: /tmp # The classloading resolve order. Possible values are 'child-first' (Flink's default)
# and 'parent-first' (Java's default).
#
# Child first classloading allows users to use different dependency/library
# versions in their application than those in the classpath. Switching back
# to 'parent-first' may help with debugging dependency issues.
#
# classloader.resolve-order: child-first # The amount of memory going to the network stack. These numbers usually need
# no tuning. Adjusting them may be necessary in case of an "Insufficient number
# of network buffers" error. The default min is 64MB, the default max is 1GB.
#
# taskmanager.memory.network.fraction: 0.1
# taskmanager.memory.network.min: 64mb
# taskmanager.memory.network.max: 1gb

Flink集群安全配置

#==============================================================================
# Flink Cluster Security Configuration
#============================================================================== # Kerberos authentication for various components - Hadoop, ZooKeeper, and connectors -
# may be enabled in four steps:
# 1. configure the local krb5.conf file
# 2. provide Kerberos credentials (either a keytab or a ticket cache w/ kinit)
# 3. make the credentials available to various JAAS login contexts
# 4. configure the connector to use JAAS/SASL # The below configure how Kerberos credentials are provided. A keytab will be used instead of
# a ticket cache if the keytab path and principal are set. # security.kerberos.login.use-ticket-cache: true
# security.kerberos.login.keytab: /path/to/kerberos/keytab
# security.kerberos.login.principal: flink-user # The configuration below defines which JAAS login contexts # security.kerberos.login.contexts: Client,KafkaClient

Zookeeper安全配置

#==============================================================================
# ZK Security Configuration
#============================================================================== # Below configurations are applicable if ZK ensemble is configured for security # Override below configuration to provide custom ZK service name if configured
# zookeeper.sasl.service-name: zookeeper # The configuration below must match one of the values set in "security.kerberos.login.contexts"
# zookeeper.sasl.login-context-name: Client #==============================================================================
# HistoryServer
#============================================================================== # The HistoryServer is started and stopped via bin/historyserver.sh (start|stop) # Directory to upload completed jobs to. Add this directory to the list of
# monitored directories of the HistoryServer as well (see below).
#jobmanager.archive.fs.dir: hdfs:///completed-jobs/ # The address under which the web-based HistoryServer listens.
#historyserver.web.address: 0.0.0.0 # The port under which the web-based HistoryServer listens.
#historyserver.web.port: 8082 # Comma separated list of directories to monitor for completed jobs.
#historyserver.archive.fs.dir: hdfs:///completed-jobs/ # Interval in milliseconds for refreshing the monitored directories.
#historyserver.archive.fs.refresh-interval: 10000

最新文章

  1. Log4net入门(WCF篇)
  2. android开发------第一个android程序
  3. 一. HTML认识
  4. Altium Designer中默认取消重复画线的选项
  5. OC中的字符串常用方法
  6. XFire构建服务端Service的两种方式
  7. cocos2dx 在mac下开发ios和android游戏
  8. 首页商品图片显示错位,easy-popular批量上传
  9. 多重影分身——C#中多线程的使用三(调用方法和传参)
  10. 【转】Sentry介绍
  11. text-shadow 详解及示例
  12. mysql5.7安装记录
  13. Apache Spark as a Compiler: Joining a Billion Rows per Second on a Laptop(中英双语)
  14. 《CSS世界》读书笔记(一)
  15. 《微信小程序组件》收集
  16. 在浏览器中使用Javascript
  17. Steeltoe之Config客户端篇
  18. Dropout正则化和其他方法减少神经网络中的过拟合
  19. glibc源码下载
  20. SPFA 上手题 数 枚:

热门文章

  1. 使用openssl做CA服务器,并且生成证书。
  2. Bandwagon 安装 Mysql 数据库
  3. 1.1 js中函数定义解析(学习笔记)
  4. 19 01 15 django 数据库设计模型 管理站点 注意:在引入外键在django 2以上改版
  5. zabbix监控日志关键字
  6. linux 替换jdk指定jar包
  7. 201703-1 分蛋糕 Java
  8. SQL基础教程(第2版)第2章 查询基础:练习题
  9. UML-架构分析-步骤
  10. UML-迭代2:更多模式