Bug #7936
Same pid with different status exists in the index_task table
0%
Description
Dave ran this command in the cn-stage (cci 2.3.0) and got 8 reults:
d1-index-queue=> select TIMESTAMP 'epoch' + taskmodifieddate/1000 * INTERVAL '1 second' as tmd, pid from index_task where status = 'NEW' and pid in (select pid from index_task where status='IN PROCESS') order by tmd;
tmd | pid
---------------------+------------------------------------------------------------
2016-11-16 17:30:39 | resource_map_doi:10.18739/A26D05
2016-11-16 17:32:03 | resource_map_urn:uuid:8a304471-d3a7-46e9-ab7d-01647cedff56
2016-11-16 19:31:45 | resource_map_doi:10.18739/A2R636
2016-11-16 20:44:49 | resource_map_urn:uuid:ff9f3613-4128-4055-83e2-861a4bf4e15f
2016-11-16 20:44:59 | resource_map_doi:10.18739/A2X31Z
2016-11-16 20:51:42 | resource_map_urn:uuid:cf21dcbf-4c51-4c3e-83d5-fa8f03ba3f95
2016-11-16 21:00:58 | resource_map_urn:uuid:166be277-4c1e-47c5-8e39-2b3de95a6743
2016-11-16 21:00:58 | resource_map_urn:uuid:ac57b649-0c69-4837-bc0b-1cdd838321d6
(8 rows)
He ran the command again and got 141 results.
We need figure out why this happened.
History
#1 Updated by Dave Vieglais over 7 years ago
- Target version changed from CCI-2.3.1 to CCI-2.3.2
#2 Updated by Jing Tao about 7 years ago
- Target version changed from CCI-2.3.2 to CCI-2.4.0
