When scaling container horizontally - local cache for the request isn't accessible across replicas

When running mod-data-import in production, it is desirable to scale the module horizontally for availability and performance. The request gets locally cached in the module - and that cached space isn't shared between the replicas. Thus, if one module replica takes the request, and another replica processes it, and lastly another replica actually does the load - the cached data file is unavailable and the error is thus:

19:00:09.749 [processing-files-thread-pool-3] ERROR ileChunkingProcessor [56312257eqId] Can not process file: ./storage/upload/629c1ad7-4134-4466-9df1-ddef0cc93464/0e3155c0-d7a0-4e6f-bad7-5697bde9a3df/amdb_sample.mrc. Cause: Can not initialize reader. Cause: File './storage/upload/629c1ad7-4134-4466-9df1-ddef0cc93464/0e3155c0-d7a0-4e6f-bad7-5697bde9a3df/amdb_sample.mrc' does not exist

java.lang.IllegalArgumentException: Can not initialize reader. Cause: File './storage/upload/629c1ad7-4134-4466-9df1-ddef0cc93464/0e3155c0-d7a0-4e6f-bad7-5697bde9a3df/amdb_sample.mrc' does not exist

It may be desirable to present this cached space to the module as shared storage - such as NFS.