fineract-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [fineract] edcable commented on pull request #1187: FINERACT-1037: Adding persistent volume for Fineract imports
Date Wed, 19 Aug 2020 23:26:34 GMT

edcable commented on pull request #1187:

   @Nayan had this feedback to share on this issue:
   The cause is the system trying to access a file that simply does not exist. Most importantly
we need to understand what scenarios system can get into this state.
   1. You get this error if you recreate your Fineract docker image but you do not recreate
your MySQL database ( as mentioned in the FINERACT-1037), this rarely happens and not the
real reason for the error.
   2. When deployed Fineract in clustered mode but storage pointed to the local file system,
instead of to a shared network mounted files system
   3. In the system configuration if they switch from storage from file system to S3 and then
from S3 back to file system ( Fineract does not remember the files was stored in S3 or Filesystem
it simply tries to access with present configuration )
   - This PR might only fix problem number two.  
   - The issue number one is more of DevOps, we should not worry about it. 
   - A most important and possible our user may face is the third one, we need to solve is
the third one (I have not tested the third one on the latest codebase, assumed based on my
past experience)

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

View raw message