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 20:57:34 UTC

[jira] [Commented] (VCL-758) VCL timings - make various timings to be variables and edited by admin

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

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

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

VCL-308
inserted loadlog entry for image copy

VCL-568
added loadstatenames for frontend to montior connect for refresh

VCL-758
removed check/restriction for connecttimeout. Previously it would not allow less than 10min. Now can allow down to 1 min

VCL-799
update_cluster, changed routine name in reserved

> VCL timings - make various timings to be variables and edited by admin 
> -----------------------------------------------------------------------
>
>                 Key: VCL-758
>                 URL: https://issues.apache.org/jira/browse/VCL-758
>             Project: VCL
>          Issue Type: Improvement
>          Components: database, vcld (backend), web gui (frontend)
>            Reporter: Aaron Peeler
>            Priority: Minor
>             Fix For: 2.4
>
>
> Allow VCL admins edit some of the timing values via the front-end.
> Possible variables to allow edits are:
> acknowledge timeout = time limit to wait on user to hit connect button
> connect timeout =  wait for user to connect for normal reservations
> ignore_connections_gte = skip checks for durations gte X (24hrs is hardcoded in code)
> general_inuse_check = how often to check on normal reservations
> server_inuse_check = how often to check on server reservations
> cluster_inuse_check = how often to check on cluster reservations
> Some of these can easily be setup based on an affiliation, but others we may want to limit as a global setting such as general_inuse_check.
> Need a page on the web portal for admins to set the values.
> List of times for variable table and their default times being set in backend:
> acknowledgetimeout => '900',
> connecttimeout => '900',
> wait_for_reconnect => '900',
> general_inuse_check => '300',
> server_inuse_check => '900',
> cluster_inuse_check => '900',
> general_end_notice_first => '600',
> general_end_notice_second => '300',
> ignore_connections_gte => '1440'



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