CDR Tickets

Issue Number 3963
Summary Simplify Rerunning Jobmaster Job (Linux)
Created 2015-08-31 15:45:18
Issue Type Improvement
Submitted By Englisch, Volker (NIH/NCI) [C]
Assigned To Englisch, Volker (NIH/NCI) [C]
Status Closed
Resolved 2016-04-06 17:59:53
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.168919
Description

If the CDR publishing job failed to run and is rerun on the following Monday the file names indicating the week number of the publishing job are off by 1. In order for the email notification to complete successfully, which is looking for a file with a date from the previous week, some of the file names need to be renamed.

We want to modify the process so that renaming of the file names happens automatically in the event that a publishing job will have to be submitted manually.

Comment entered 2016-02-18 11:21:25 by Learn, Blair (NIH/NCI) [C]

Linux, Python

Can this be run on Windows and the data pushed to Linux? Can the Linux server in this be replaced by an NFS mount on the Windows server?

Depends on having a job scheduler and making this a plugin of the scheduler, albeit this is on a different server.

Estimate: 8

Comment entered 2016-04-06 17:59:38 by Englisch, Volker (NIH/NCI) [C]

The following program has been modified:

  • R13853: Jobmaster.py

The job is usually submitted with two parameters as

$ Jobmaster.py --livemode --export

When it needs to be submitted manually the ISO week number needs to be specified:

$ Jobmaster.py --livemode --export --week=201613

This will run the job using the latest *.tar.gz file located in the directory:

/usr/local/cdr/qa/pdq/incoming/full/

Testing completed successfully. An entry has been added to the crontab table listing the command with --week parameter.

Comment entered 2016-05-13 16:25:45 by Englisch, Volker (NIH/NCI) [C]

These changes can not easily be tested on PROD unless a regular publishing job failed.

Closing ticket.

Elapsed: 0:00:00.001324