[ 
https://issues.apache.org/jira/browse/YARN-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643328#comment-14643328
 ] 

Anubhav Dhoot commented on YARN-3736:
-------------------------------------

bq. It may be better to store ReservationId object rather than the name as we 
are parsing the name back in most places
Since the reservationId is used as a key/path where the 
ReservationAllocationState is stored, we need to convert the reservationId to 
string format. We are not actually storing the reservationId as part of the 
protobuf payload anymore. 

> Persist the Plan information, ie. accepted reservations to the RMStateStore 
> for failover
> ----------------------------------------------------------------------------------------
>
>                 Key: YARN-3736
>                 URL: https://issues.apache.org/jira/browse/YARN-3736
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler, fairscheduler, resourcemanager
>            Reporter: Subru Krishnan
>            Assignee: Anubhav Dhoot
>         Attachments: YARN-3736.001.patch, YARN-3736.001.patch, 
> YARN-3736.002.patch
>
>
> We need to persist the current state of the plan, i.e. the accepted 
> ReservationAllocations & corresponding RLESpareseResourceAllocations  to the 
> RMStateStore so that we can recover them on RM failover. This involves making 
> all the reservation system data structures protobuf friendly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to