https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6886
--- Comment #6 from Kevin A. McGrail <kmcgr...@pccc.com> --- As of today, I believe we are about 99% operational on rule updates/masscheck/ruleqa on zones2 and sa-vm (zones replacement). So we are getting there. I emailed infra today about merging zones and zones2: I'm working on spamassassin.zones (the box that died) and spamassassin2.zones (a box that it is still running) and looking at merging it now that we have a modern os with a few other boxes outside of ASF Infrastructure. I know we will likely need a lot more ram, processors, etc. (we apparently bring an 8 core/16GB/15K RPM Scsi box to it's knees every 4 hours). However, while researching things for the crashed box, I stumbled on this note: http://marc.info/?l=spamassassin-devel&m=123595497214124&w=4 >http://ruleqa.spamassassin.org/ has been moved from >spamassassin.zones.apache.org to spamassassin2.zones, at the request >of ASF infrastructure. everything should be working OK now, but shout >if you see anything odd... My concern is I don't know WHY infra requested we split the boxes and I fear I'm about to tread down the same path by working to merge them. Do you have the ability to search and see if there are any emails with infra about this issue and why infra requested the project split up our processing? By all the notes I've seen, spamassassin2.zones.apache.org is considered a "beefy" box and it grinds a lot. -- You are receiving this mail because: You are the assignee for the bug.
