You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Josh Thompson (JIRA)" <ji...@apache.org> on 2015/08/10 21:39:47 UTC
[jira] [Commented] (VCL-846) Improve flow of handling nodes for
deleted reservations assigned to new reservations
[ https://issues.apache.org/jira/browse/VCL-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680640#comment-14680640 ]
Josh Thompson commented on VCL-846:
-----------------------------------
I prefer option 2 or 3 because small installations could end up saying nothing is currently available when there are nodes that are just being preloaded for new reservations.
> Improve flow of handling nodes for deleted reservations assigned to new reservations
> ------------------------------------------------------------------------------------
>
> Key: VCL-846
> URL: https://issues.apache.org/jira/browse/VCL-846
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend), web gui (frontend)
> Reporter: Aaron Peeler
> Fix For: 2.5
>
>
> As a user can make a new reservation, the front-end can assign a node that is currently being cleaned up from a deleted reservation. So far the states observed are:
> currentstate = pending
> laststate = deleted
> node state = reserved
> If this node is assigned to a new reservation, the back end checks for existing process, logs it and fails the new reservation. It fails it likely because the new process on the backend does not know how much time is left to clean up the deleted reservation.
> A decision/implementation on synchronizing the front-end and back-end needs to be made on how to handle this case as to not have reservation failures.
> Suggestions are to:
> 1) only select available machines not assigned to reservations on the front end.
> 2) Or on the backend - wait until the previous deleted process is complete( which could take a while depending on what can be done)
> 3) on the backend - intercept the process and force a reload - not matter what the image is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)