[
https://issues.apache.org/jira/browse/YARN-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated YARN-6354:
-----------------------------
Priority: Major (was: Critical)
Summary: LeveldbRMStateStore can parse invalid keys when recovering
reservations (was: RM fails to upgrade to 2.8 with leveldb state store)
I found another instance where a rolling upgrade to 2.8 with leveldb did work
successfully, so I dug a bit deeper into why this doesn't always fail. It
turns out that normally the reservation state keys happen to be the last keys
in the database and therefore it works. If the database happens to have any
relatively short keys after the reservation keys then it breaks. My local dev
database had some short, lowercase keys leftover in it from some prior work,
and that's how I ran into the issue.
Since it looks like this happens to not be a problem for now with "normal" RM
leveldb databases I lowered the severity and updated the headline accordingly.
> LeveldbRMStateStore can parse invalid keys when recovering reservations
> -----------------------------------------------------------------------
>
> Key: YARN-6354
> URL: https://issues.apache.org/jira/browse/YARN-6354
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.8.0
> Reporter: Jason Lowe
>
> When trying to upgrade an RM to 2.8 it fails with a
> StringIndexOutOfBoundsException trying to load reservation state.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
