[
https://issues.apache.org/jira/browse/FLINK-15488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009653#comment-17009653
]
Yang Wang edited comment on FLINK-15488 at 1/9/20 4:31 AM:
-----------------------------------------------------------
[~gjy] We use {{org.apache.flink.runtime.util.BashJavaUtils}} to calculate the
ResourceDynamicConfigs and ResourceJvmParams. When using logback, the
configuration logs will show up in the stdout. So the timestamp in the log is
wrongly regarded as the class.
You could verify this by the following step.
1. Use
[logback|https://ci.apache.org/projects/flink/flink-docs-stable/dev/best_practices.html#use-logback-when-running-flink-on-a-cluster]
2. Running the following command
{code:java}
java -classpath "lib/*" org.apache.flink.runtime.util.BashJavaUtils
GET_TM_RESOURCE_JVM_PARAMS --configDir /tmp/flink-release/conf
{code}
3. Then you could get the following output.
{code:java}
19:35:57.383 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: jobmanager.rpc.address, localhost
19:35:57.387 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: jobmanager.rpc.port, 6123
19:35:57.387 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: jobmanager.heap.size, 1024m
19:35:57.387 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: taskmanager.memory.process.size, 1024m
19:35:57.388 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: taskmanager.numberOfTaskSlots, 1
19:35:57.388 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: parallelism.default, 1
19:35:57.388 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: jobmanager.execution.failover-strategy, region
-Xmx268435450 -Xms268435450 -XX:MaxDirectMemorySize=214748366
-XX:MaxMetaspaceSize=134217728
{code}
was (Author: fly_in_gis):
[~gjy] We use {{org.apache.flink.runtime.util.BashJavaUtils}} to calculate the
ResourceDynamicConfigs and ResourceJvmParams. When using logback, the
configuration logs will show up in the stdout. So the timestamp in the log is
wrongly regarded as the class.
You could verify this by the following step.
1. Use
[logback|[https://ci.apache.org/projects/flink/flink-docs-stable/dev/best_practices.html#use-logback-when-running-flink-on-a-cluster]]
2. Running the following command
{code:java}
java -classpath "lib/*" org.apache.flink.runtime.util.BashJavaUtils
GET_TM_RESOURCE_JVM_PARAMS --configDir /tmp/flink-release/conf
{code}
3. Then you could get the following output.
{code:java}
19:35:57.383 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: jobmanager.rpc.address, localhost
19:35:57.387 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: jobmanager.rpc.port, 6123
19:35:57.387 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: jobmanager.heap.size, 1024m
19:35:57.387 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: taskmanager.memory.process.size, 1024m
19:35:57.388 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: taskmanager.numberOfTaskSlots, 1
19:35:57.388 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: parallelism.default, 1
19:35:57.388 [main] INFO org.apache.flink.configuration.GlobalConfiguration -
Loading configuration property: jobmanager.execution.failover-strategy, region
-Xmx268435450 -Xms268435450 -XX:MaxDirectMemorySize=214748366
-XX:MaxMetaspaceSize=134217728
{code}
> Cannot start a taskmanger if using logback
> ------------------------------------------
>
> Key: FLINK-15488
> URL: https://issues.apache.org/jira/browse/FLINK-15488
> Project: Flink
> Issue Type: Bug
> Components: API / Core, Deployment / Scripts
> Affects Versions: 1.10.0
> Reporter: Dawid Wysakowicz
> Assignee: Yangze Guo
> Priority: Blocker
> Fix For: 1.10.0
>
>
> When using logback it is not possible to start the taskmanager using
> {{taskamanger.sh}} scripts. The same problem (probably) occurs when using
> slf4j that logs into the console.
> The problem is that when calculating memory configuration with
> {{BashJavaUtils}} class the result is returned through standard output. If
> something is logged into the console it may result in undefined behavior such
> as e.g.
> {code}
> Error: Could not find or load main class 13:51:23.961
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
