[
https://issues.apache.org/jira/browse/YARN-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844556#comment-16844556
]
Bibin A Chundatt commented on YARN-9568:
----------------------------------------
[[email protected]]
Nodelabel had a configuration to enabled or disable the store. NodeAttributes
store is enabled by default [~sunilg]/[~cheersyang]
{quote}
Any error in loading should be treated as no data to recover
{quote}
Old nodelabel store had the same behaviour any invalid file used to fail RM
startup. The logs really need improvement.
For MiniYarnCluster we could configure the node atttribute store path to
unique folder inside targetWorkDir.
This could solve the issue rt ?
> NPE in MiniYarnCluster during FileSystemNodeAttributeStore.recover
> ------------------------------------------------------------------
>
> Key: YARN-9568
> URL: https://issues.apache.org/jira/browse/YARN-9568
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, test
> Affects Versions: 3.3.0
> Environment: macos
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: npe.log
>
>
> This seems new in trunk. As in "wasn't happening a couple of weeks ago". Its
> surfacing in the S3A committer tests which are trying to create
> MiniYarnClusters: all such tests are failing as the mini yarn cluster won't
> come up with an NPE in {{FileSystemNodeAttributeStore.recover}}
> I'm not sure why node labels are needed on test clusters; the default implies
> they should be off anyway.
> At the same time, I can't seem to find one specific change in the git log to
> say "this is causing the problem".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
