Project

General

Profile

Bug #15332

Some jobs have two job_histories records for one job.

Added by Stephen White over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
02/02/2017
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
First Occurred:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

A job should have only one job_histories record with a status of 'Completed'

pomsprd=> select * from job_histories where job_id=919415;
job_id | created | status
--------+-------------------------------+-----------
919415 | 2017-01-19 09:22:47.124782-06 | Idle
919415 | 2017-01-19 09:25:08.824414-06 | Completed
919415 | 2017-01-19 09:26:01.509837-06 | Running
919415 | 2017-01-19 09:28:40.216064-06 | Completed
919415 | 2017-01-25 13:35:50.815661-06 | Located
(5 ro


Subtasks

Bug #15442: Correct jobs in DB with multiple 'Completed' statuses.ClosedStephen White

History

#1 Updated by Stephen White over 3 years ago

As of today here are the number of jobs with duplicates grouped by the number of duplicates.

 count_all | Num_jobs_with_duplicates
-----------+-------
         2 |   964
         3 |   171
         4 |   234
         5 |    17
         6 |    26
         7 |    79
        28 |   100

#2 Updated by Marc Mengel over 3 years ago

  • Status changed from New to Work in progress
  • Target version set to v2_0_0

Trying a fix to delete any existing Completed items from job history if we're marking the job Completed.

#3 Updated by Marc Mengel over 3 years ago

  • % Done changed from 0 to 70

#4 Updated by Marc Mengel over 3 years ago

  • Status changed from Work in progress to Resolved

#5 Updated by Marc Mengel over 3 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF