Bug #7072
LogAggregatorTask ends when processing a pid that has been deleteded
Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_log_aggregation
Target version:
Start date:
2015-04-30
Due date:
% Done:
100%
Story Points:
Sprint:
Description
In the sandbox env with the CCI 1.5.1 beta build, the LogAggregatorTask ends when harvesting log records from cnSandboxUNM1 when it processes pid doi:10.6073/pasta/bfa982d1d1bf7e23c505bf9243011988.
This pid does not have a system metadata entry, i.e. https://cn-sandbox-unm-1.test.dataone.org/cn/v1/meta/doi:10.6073/pasta/bfa982d1d1bf7e23c505bf9243011988 returns status 500, but it does have
access log entries returned from https://cn-sandbox-unm-1.test.dataone.org/metacat/d1/cn/log?start=2014-11-26T05:01.47.001&count=5000. I suspect that this task is ending
when it tries to get the sysmeta record for this pid at LogAggregatorTask: solrItem.updateSysmetaFields(systemMetadata);
History
#1 Updated by Skye Roseboom over 9 years ago
- Assignee set to Peter Slaughter
- Target version set to CCI-1.5.1
#2 Updated by Peter Slaughter over 9 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Fix tested in sandbox environment.