Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
doujutun3207
flink
提交
d0debf4a
F
flink
项目概览
doujutun3207
/
flink
与 Fork 源项目一致
从无法访问的项目Fork
通知
24
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
F
flink
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
d0debf4a
编写于
9月 20, 2017
作者:
D
desktop
提交者:
Tzu-Li (Gordon) Tai
9月 22, 2017
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
[hotfix] Fix typo in Debugging Classloading documentation
This closes #4685.
上级
6c1a9465
变更
1
显示空白变更内容
内联
并排
Showing
1 changed file
with
5 addition
and
5 deletion
+5
-5
docs/monitoring/debugging_classloading.md
docs/monitoring/debugging_classloading.md
+5
-5
未找到文件。
docs/monitoring/debugging_classloading.md
浏览文件 @
d0debf4a
...
...
@@ -28,7 +28,7 @@ under the License.
## Overview of Classloading in Flink
When running Flink applications, the JVM will load various classes over time.
These classes can be d
e
vided into two domains:
These classes can be d
i
vided into two domains:
-
The
**Flink Framework**
domain: This includes all code in the
`/lib`
directory in the Flink directory.
By default these are the classes of Apache Flink and its core dependencies.
...
...
@@ -41,12 +41,12 @@ The class loading behaves slightly different for various Flink setups:
**Standalone**
When starting a
the
Flink cluster, the JobManagers and TaskManagers are started with the Flink framework classes in the
When starting a Flink cluster, the JobManagers and TaskManagers are started with the Flink framework classes in the
classpath. The classes from all jobs that are submitted against the cluster are loaded
*dynamically*
.
**YARN**
YARN classloading differs between single job deploymens and sessions:
YARN classloading differs between single job deploymen
t
s and sessions:
-
When submitting a Flink job directly to YARN (via
`bin/flink run -m yarn-cluster ...`
), dedicated TaskManagers and
JobManagers are started for that job. Those JVMs have both Flink framework classes and user code classes in their classpath.
...
...
@@ -65,7 +65,7 @@ classes are loaded dynamically when the jobs are submitted.
## Avoiding Dynamic Classloading
All components (JobManger, TaskManager, Client, ApplicationMaster, ...) log their classpath setting on startup.
They can be found as part of the environment information at the beginni
gn
of the log.
They can be found as part of the environment information at the beginni
ng
of the log.
When running a setup where the Flink JobManager and TaskManagers are exclusive to one particular job, one can put JAR files
directly into the
`/lib`
folder to make sure they are part of the classpath and not loaded dynamically.
...
...
@@ -76,7 +76,7 @@ Because the AppClassLoader is the parent of the FlinkUserCodeClassLoader (and Ja
result in classes being loaded only once.
For setups where the job's JAR file cannot be put to the
`/lib`
folder (for example because the setup is a session that is
used by multiple jobs), it may still be posible to put common libraries to the
`/lib`
folder, and avoid dynamic class loading
used by multiple jobs), it may still be pos
s
ible to put common libraries to the
`/lib`
folder, and avoid dynamic class loading
for those.
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录