// We limit the number of Notifications that this job will update to 2,000 for performance reasons.
// For larger numbers, the EF context was becoming very large, and the job was slowing down considerably.
// We would only expect a large number of updates to be needed here following a large migration. In this
// scenario, the job should be run manually to import all the data (and if this is forgotten then we
// trigger a warning in Sentry).
public async Task Run(IJobCancellationToken token)
{
Log.Information($"Starting Drug resistance profile update job");
var numberOfNotificationsStillNeedingUpdate = await _service.UpdateDrugResistanceProfiles(MaxNumberOfUpdatesPerRun);
var totalNumberOfNotificationsRequiredAtStartOfRun = numberOfNotificationsStillNeedingUpdate + MaxNumberOfUpdatesPerRun;
if (numberOfNotificationsStillNeedingUpdate > 0)
{
Log.Warning($"Discovered {totalNumberOfNotificationsRequiredAtStartOfRun} Notifications which require updates to their " +
$"Drug Resistance Profile. The Drug Resistance Profile update job will only handle {MaxNumberOfUpdatesPerRun} " +
$"Notifications per run, so there are still {numberOfNotificationsStillNeedingUpdate} Notifications which " +
"need to be updated. Trigger the job manually in order to update these Notifications.");
}
Log.Information($"Finishing Drug resistance profile update job");
}
private async Task UpdateDrugResistanceProfiles(
PerformContext context,
int runId,
List <Notification> savedNotifications)
{
try
{
await _drugResistanceProfileService.UpdateDrugResistanceProfiles(savedNotifications);
}
catch (Exception e)
{
Log.Error(e, e.Message);
await _logger.LogGroupWarning(context, runId, savedNotifications,
"An error occurred while attempting to update the drug resistance profiles for the group." +
" The drug resistance profile update job should be run when the import finishes to fix this issue.");
}
}