Bug 536867 - Need to throttle/prohibit any syncs that allow per-second granularity.
Summary: Need to throttle/prohibit any syncs that allow per-second granularity.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Content
Version: unspecified
Hardware: All
OS: Linux
low
high
Target Milestone: ---
: ---
Assignee: Charles Crouch
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: rhq_spearhead rhq_core_next
TreeView+ depends on / blocked
 
Reported: 2009-11-11 16:30 UTC by Corey Welton
Modified: 2015-02-01 23:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-02 17:57:17 UTC
Embargoed:

Attachments (Terms of Use)

Description Corey Welton 2009-11-11 16:30:07 UTC 
Description of problem:

The cron-esque quartz scheduler used in rhq has six fields - not five.  One of these is for seconds, and we certainly don't need/want that kind of granularity, least of all for content sync.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Go to sync schedule in content 
2.  Modify sync cronjob to read "*/1 * * * * ?"; submit
3.  Watch your server logs as you attempt to sync every second.
  
Actual results:

Too many synchs scheduled.

Expected results:

Probably need to kill any ability to schedule per-second...


Additional info:
Comment 1 wes hayutin 2010-02-16 16:57:20 UTC 
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug
Comment 2 wes hayutin 2010-02-16 17:02:26 UTC 
making sure we're not missing any bugs in rhq_triage
Note You need to log in before you can comment on or make changes to this bug.