Review state control of module

Description

Purpose/Overview:
In order to achieve a possibility to run multiple instances of the same module state control verification should be done.
For better understanding see parent story https://folio-org.atlassian.net/browse/FOLIO-2725

Acceptance criteria:

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Kruthi Vuppala September 17, 2020 at 6:38 PM

There is no matrix to be filled on the WIKI page. As per verification of stateless

  • data-export doesn't store any session data - It gets details for running a job from various APIs internal to data-export and few APIs are external

  • It does store cache locally before triggering a job, but that is job specific, and cache is expired after a given job. Also each job-execution runs on only one instance. There is no way for it to be split among instances. So it is scalable

  • File upload functionality is the only part which is not horizontally scalable at this point. There is already some discussion in
    https://docs.google.com/document/d/1kmafhus497R5UF1D3GxJb3QoJMRPvBdadfolGVkq6G0/edit?pli=1 - to be taken care by the hosting service
    and
    also a POC being checked https://folio-org.atlassian.net/browse/MDEXP-90 in case that is not fruitful.

Conclusion:

  • data-export is horizontally scalable if file upload is taken out of picture

Kruthi Vuppala September 3, 2020 at 2:27 PM

Note: There is a WIKI page going to be created to decide the points to check for , we will probably wait until that WIKI page is agreed on by the community to complete this story

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Concorde

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created August 18, 2020 at 1:21 PM
Updated October 14, 2020 at 12:41 PM
Resolved September 18, 2020 at 7:43 PM
TestRail: Cases
TestRail: Runs