Uploaded image for project: 'GPII - Global Public Inclusive Infrastructure'
  1. GPII - Global Public Inclusive Infrastructure
  2. GPII-4106

Make the Morphic applications more resilient to network and DB errors

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: core
    • Labels:
      None

      Description

      The network communication between each piece of the architecture can have unexpected problems at any time. Possible scenarios can be:

      • Network issues between the client and the cloud
      • Network issues between flowmanager and preferences-server
      • Network issues between preferences server and CouchDB

      Also the CouchDB can return non 200 replies if any problem occurs in the database. Possible scenarios can be:

      • A rolling update of the CouchDB cluster. Where the restart of a node can cause a never ended request response or a 500 error returned to preferences-server during the node restart.
      • A conflict of the data write. A possible scenario can be two simultaneous data write to the same data point but sent to different nodes and the nodes weren't able to determine which request was first. We have detected this behavior when the cluster was recovering from a transient inconsistent mode and the Locust process were performing the load tests at the same time.

        Attachments

          Activity

            People

            Assignee:
            jhernandez Javier Hernández
            Reporter:
            amatas Alfredo Matas
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: