[YARN-7601] Incorrect container states recovered as LevelDB uses alphabetical order

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Target Version/s: 2.9.3
• Assignee: Sampada Dehankar
• Reporter: Sampada Dehankar
• Created: 03/Dec/17 09:51
• Updated: 01/Nov/18 06:35

Description

LevelDB stores key-value pairs in the alphabetical order. Container id concatenated by its state is used as key. So, even if container goes through any states in its life cycle, the order of states for following values retrieved from LevelDB is always going to be as below`:

LAUNCHED
PAUSED
QUEUED

For eg: If a container is LAUNCHED then PAUSED and LAUNCHED again, the recovered container state is PAUSED currently instead of LAUNCHED.
We propose to store the timestamp as the value while making call to

storeContainerLaunched
storeContainerPaused
storeContainerQueued

so that correct container state is recovered based on timestamps.