[
https://issues.apache.org/jira/browse/YARN-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914435#comment-16914435
]
Prabhu Joseph commented on YARN-9776:
-------------------------------------
This happens when NodeManager aggregates the log files in IFile format whereas
the client (yarn logs command) machine uses TFile format. Can you make sure
{{yarn.log-aggregation.file-formats}} config is set to same value in both NM
and Client machine.
Setting yarn.log-aggregation.file-formats to IFile in Client machine would have
solved the issue. We should not remove the meta file.
And this is not related to
{{yarn.timeline-service.generic-application-history.save-non-am-container-meta-info}}.
> yarn logs throws an error "Not a valid BCFile"
> ----------------------------------------------
>
> Key: YARN-9776
> URL: https://issues.apache.org/jira/browse/YARN-9776
> Project: Hadoop YARN
> Issue Type: Bug
> Components: log-aggregation
> Affects Versions: 3.1.0
> Environment: HDP 3.1.0.78
>
> Reporter: agoodboy
> Priority: Major
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Env: hdp 3.1.0.0-78
> Command: yarn logs -applicationId xxx, throws an error "Not a valid BCFile.",
> and then exit.
> After open debug log using "export YARN_ROOT_LOGGER="DEBUG,console", and
> rerun command. It shows that
> "fileName=/data1/app-logs/hadoop/logs/application_1566555356033_0032/meta" is
> not a valid BCFile. And after I remove the file from hdfs, and rerun command,
> it success.
> So, how to generate this meta file?
> I guess that is because this in yarn-site.xml:
> <property>
>
> <name>yarn.timeline-service.generic-application-history.save-non-am-container-meta-info</name>
> <value>true</value>
> </property>
> I set this value to true because I want to see all container logs in timeline
> web page, orelse I can just see the am container log.
> So, it seems that yarn logs can't properly handle this suituation.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
