Issue Number | 4266 |
---|---|
Summary | Eliminate CDR publishing service |
Created | 2017-05-10 09:41:24 |
Issue Type | Improvement |
Submitted By | Kline, Bob (NIH/NCI) [C] |
Assigned To | Kline, Bob (NIH/NCI) [C] |
Status | Closed |
Resolved | 2017-08-15 11:22:05 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.207942 |
In order to reduce the footprint of the CDR system, we have decided to eliminate the Windows service for CDR publishing. The functionality performed by this service includes
check for queued publishing jobs and launch them
check for queued batch jobs (e.g., long-running reports) and launch them
verify successful completion of jobs to push documents to GateKeeper
This functionality will be moved to tasks running under the new CDR scheduler.
finish implementation ✔
disable cdrpublish2 service on DEV ✔
test on DEV ✔
code walkthrough ✔
resolve scheduler failures ✔
create deployment package/script/instructions ✔
deploy to QA ✔
test on QA ✔
deploy to STAGE ✔
test on STAGE ✔
deploy to production ✔
Making good progress. Things look very promising for the reconfiguration of the scheduler, so I've checked off the "resolve failures" item. I have a package rolled with a "double-click this file" deployment for CBIIT which I've tested on DEV and QA. Next week we should be able to put it on STAGE, assuming no surprises on the lower two tiers. I've got the sweeps of the publishing and batch jobs queues set to run once each minute, and the verification of push jobs set to run every two minutes. Do you recommend any adjustments to these intervals, ~volker?
The deployment script lives at:
nciis-p401.nci.nih.gov\cdr_deployments\replace-publishing-service\deploy.bat
It uninstalls both of the publishing services which Rob Chen set up for us (after backing up the registry settings for the one we've been using most recently).
[EDIT]: All done - closing ticket.
~volker: I see you've got the Jobmaster Nightly task disabled on QA and the Jobmaster Weekly set to run Sunday through Thursday on that tier. Do you need to keep QA configured that way for now (as part of your work on OCECDR-4268)? I don't have a strong opinion one way or another.
No, it doesn't need to stay this way. We'll have to test again once we have the production FTP server from CBIIT. It's OK to make changes now that everything is working correctly.
I've got the sweeps of the publishing and batch jobs queues set to run once each minute, and the verification of push jobs set to run every two minutes.
We currently don't run the verification this frequently (I think) but anything better than 5 minutes is great.
Elapsed: 0:00:00.000721