-
Story
-
Resolution: Fixed
-
Major
-
None
-
SIdora Sprint 73
The EDAN/IDS integration lags far behind Camera Trap ingest making it difficult to operate the system. While the integration is robust as it is driven by JMS messages that are persisted until completed, lags of a day or more are experienced before the images become available for emammal. This results in images that are index but cannot be accessed. The EDAN/IDS integation should be able to keep up with five parallel ingest pipelines. In particular, large deployments processing is very slow because it iterates sequentially over the objects. This will only get worse with the inclusion of event-driven updates.
- is blocked by
-
SID-1117 Parallelize EDAN JSON creation (Pipeline Enhancement Task 1)
- Closed
-
SID-1118 Create JSON array for EDAN bulk upload (Pipeline Enhancement Task 1)
- Closed
-
SID-1119 Upload all images to IDS dropbox before writing assetXML file (Pipeline Enhancement Task 1)
- Closed
-
SID-1120 Write IDS asset xml file to SIRIS dropbox (Pipeline Enhancement Task 1)
- Closed
- relates to
-
SID-1083 As a operator, I want EDAN/IDS operations to keep pace with ingests because ingest can get backed up waiting (Pipeline Enhancement Task 1)
- Closed
-
SID-1121 Set up logging for the EDAN/IDS operations via Splunk
- Created
- Wiki Page
-
Wiki Page Loading...