You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sampada Dehankar (JIRA)" <ji...@apache.org> on 2017/12/03 09:52:00 UTC

[jira] [Created] (YARN-7601) Incorrect container states recovered as LevelDB uses alphabetical order

Sampada Dehankar created YARN-7601:
--------------------------------------

             Summary: Incorrect container states recovered as LevelDB uses alphabetical order
                 Key: YARN-7601
                 URL: https://issues.apache.org/jira/browse/YARN-7601
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Sampada Dehankar
            Assignee: Sampada Dehankar


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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org