You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/11/07 18:53:18 UTC

[jira] [Commented] (VCL-734) set requests to pending state earlier when processing

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

ASF subversion and git services commented on VCL-734:
-----------------------------------------------------

Commit 1539735 from [~fapeeler] in branch 'vcl/trunk'
[ https://svn.apache.org/r1539735 ]

VCL-734

vcld: Added update_request_state before make_new_child for non-cluster requests
State.pm: moved close bracket to isolate state change to cluster reservations

> set requests to pending state earlier when processing
> -----------------------------------------------------
>
>                 Key: VCL-734
>                 URL: https://issues.apache.org/jira/browse/VCL-734
>             Project: VCL
>          Issue Type: Improvement
>          Components: vcld (backend)
>            Reporter: Aaron Peeler
>            Priority: Minor
>             Fix For: 2.4
>
>
> With some of the latest code additions. It appears reservations can be picked up a second time during vcld's initial fetch of requests that need to be processed.
> The routine update_request_state gets called in the State.pm module to update a reservation to pending, which after loading several other prov/OS modules for a request, the loop in vcld can pick up the same request and try to process again.
> So for non-cluster reservations, add a call to update_request_state in vcld before forking. Cluster requests will still likely need to be updated from the State.pm module. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)