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 2014/11/21 16:38:33 UTC
[jira] [Commented] (VCL-800) Reservations insert log.ending =
failed when they shouldn't
[ https://issues.apache.org/jira/browse/VCL-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221043#comment-14221043 ]
ASF subversion and git services commented on VCL-800:
-----------------------------------------------------
Commit 1640940 from [~arkurth] in branch 'vcl/trunk'
[ https://svn.apache.org/r1640940 ]
VCL-800
Updated utils.pm::switch_state to not set log.ending to failed if the request.state = image, checkpoint, or inuse.
Updated State.pm::reservation_failed to only update log.ending to failed if the state is new or reserved.
Other
Changed abbreviated $reservation_cnt variable in vcld to $reservation_count.
> Reservations insert log.ending = failed when they shouldn't
> -----------------------------------------------------------
>
> Key: VCL-800
> URL: https://issues.apache.org/jira/browse/VCL-800
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend)
> Affects Versions: 2.3.2
> Reporter: Josh Thompson
> Assignee: Andy Kurth
> Priority: Minor
> Fix For: 2.4
>
>
> Under some circumstances, the {{log.ending}} value may be set to _failed_ when it shouldn't. One case is when {{request.state}} is _inuse_ and vcld is unable to initialize all of the objects for one of the connection check processes. When this occurs, {{request.state}} is set back to _inuse_ but the code is currently setting {{log.ending}} to _failed_. This causes inaccurate counts on the dashboard and statistics pages on the website.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)