Bug 536867

Summary: Need to throttle/prohibit any syncs that allow per-second granularity.
Product: [Other] RHQ Project Reporter: Corey Welton <cwelton>
Component: ContentAssignee: Charles Crouch <ccrouch>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: unspecifiedCC: hbrock, jason.dobies, jshaughn, whayutin
Target Milestone: ---Keywords: SubBug
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-02 13:57:17 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Bug Depends On:    
Bug Blocks: 565635, 565650    

Description Corey Welton 2009-11-11 11:30:07 EST
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 11:57:20 EST
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 12:02:26 EST
making sure we're not missing any bugs in rhq_triage