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/10/28 23:19:27 UTC

[jira] [Commented] (VCL-874) change reloading state sooner in load process

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

Josh Thompson commented on VCL-874:
-----------------------------------

It makes sense to go ahead and do this. However, the frontend does not hand out computers that meet the following two criteria:

-assigned to a reservation where the current time falls between the reservation's start and end times
-the state of the reservation is something other than deleted, failed, or complete

So, as long as the end time of the reload reservation has not passed, the node won't be handed out to a new reservation.

> change reloading state sooner in load process
> ---------------------------------------------
>
>                 Key: VCL-874
>                 URL: https://issues.apache.org/jira/browse/VCL-874
>             Project: VCL
>          Issue Type: Bug
>          Components: vcld (backend)
>    Affects Versions: 2.4.2
>            Reporter: Aaron Peeler
>
> During reload process - change the the computer state to reloading first step.
> If the vcld process needs to copy an image from another location, the state of the computer is still in the available state - which the front end could hand out.
> By changing to reloading when vcld determines the node is to be reloaded, this avoids any conflicts.



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