You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Alan M. Carroll (JIRA)" <ji...@apache.org> on 2011/06/22 01:07:47 UTC
[jira] [Created] (TS-850) Update scheduling uses the hour offset as
a start hour.
Update scheduling uses the hour offset as a start hour.
-------------------------------------------------------
Key: TS-850
URL: https://issues.apache.org/jira/browse/TS-850
Project: Traffic Server
Issue Type: Bug
Components: Configuration
Affects Versions: 3.0.0
Reporter: Alan M. Carroll
Assignee: Alan M. Carroll
Priority: Minor
Fix For: 3.1.0
For update.config the current logic uses the hour offset as a starting hour such that if ATS is started after that hour of the day, then the next scheduled event is deferred until the next day. E.g., if the offset is 6, and ATS is started after 6AM, then the next even won't be until after 6AM the next day. Yet after the first day, events happen every interval.
Also, blank lines affect parsing, in that any configuration line following a blank line will be handled incorrectly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-850) Update scheduling uses the hour offset as
a start hour.
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan M. Carroll updated TS-850:
-------------------------------
Attachment: patch-850.txt
Changes scheduling so the next event is the next "slot" as determined by the offset and interval.
> Update scheduling uses the hour offset as a start hour.
> -------------------------------------------------------
>
> Key: TS-850
> URL: https://issues.apache.org/jira/browse/TS-850
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 3.0.0
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Priority: Minor
> Fix For: 3.1.0
>
> Attachments: patch-850.txt
>
>
> For update.config the current logic uses the hour offset as a starting hour such that if ATS is started after that hour of the day, then the next scheduled event is deferred until the next day. E.g., if the offset is 6, and ATS is started after 6AM, then the next even won't be until after 6AM the next day. Yet after the first day, events happen every interval.
> Also, blank lines affect parsing, in that any configuration line following a blank line will be handled incorrectly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-850) Update scheduling uses the hour offset
as a start hour.
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073311#comment-13073311 ]
Leif Hedstrom commented on TS-850:
----------------------------------
Alan: Are we going to land this for 3.1.0 ? Is there anything blocking just committing this?
> Update scheduling uses the hour offset as a start hour.
> -------------------------------------------------------
>
> Key: TS-850
> URL: https://issues.apache.org/jira/browse/TS-850
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 3.0.0
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Priority: Minor
> Fix For: 3.1.0
>
> Attachments: patch-850.txt
>
>
> For update.config the current logic uses the hour offset as a starting hour such that if ATS is started after that hour of the day, then the next scheduled event is deferred until the next day. E.g., if the offset is 6, and ATS is started after 6AM, then the next even won't be until after 6AM the next day. Yet after the first day, events happen every interval.
> Also, blank lines affect parsing, in that any configuration line following a blank line will be handled incorrectly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira