| Issue Number | 4084 |
|---|---|
| Summary | Spike Story: Investigate auto-restarting the Process Manager |
| Created | 2016-04-29 13:32:15 |
| Issue Type | Task |
| Submitted By | henryec |
| Assigned To | Englisch, Volker (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2017-08-15 18:35:24 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.183398 |
The Problem:
Currently, the CDR Process Manager is not configured to auto restart.
This means that often when the server is restarted during monthly
scheduled data center maintenance, the CDR Process Manager is stopped
when the server comes back up. Therefore Volker has to submit a request
to CBIIT to ask them to restart the Process Manager every time.
The Question:
Will configuring the CDR Process Manager to auto restart will fix the
problem and not introduce new problems (e.g. publishing, in GK)?
Objective of this Spike Story:
Investigate whether or not new problems will be introduced by allowing
the CDR Process manager to auto restart.
I believe the CDR Process Manager was meant to be the Gatekeeper Process Manager.
Yuen had already requested this change to be setup on STAGE. At the moment I am not certain if it has also been done on PROD.
As far as I can tell, the only remaining work is to determine if the proposed configuration change has been deployed to production, and if not have it deployed, so a low LOE estimate.
~volker is investigating whether this has been taken care of on PROD.
Volker will close this on Monday if all goes well with the weekend maintenance.
~volker: did all go well with the weekend maintenance?
Yes - for STAGE and PROD
No - for DEV and QA
Since we have access to DEV and QA to start the service ourselves we can close this ticket.
Elapsed: 0:00:00.000747