Uploaded image for project: 'onedata'
  1. onedata
  2. VFS-6189

Mechanisms for unsupport concerning dbsync and synchronizing changes

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • 22.02.0-alpha1-kuchenka
    • None
    • None
    • None

      1. Should dbsync_state be cleared in Onezone?
      2. Should provider clear its database after unsupport?
      3. Does the retiring provider need to wait for all others to learn all of its sequences? Or maybe it could transfer its sequences to another one so it can broadcast them in its name for catching  up providers?
      4. What if a new provider joins after one has retired? How can it learn the dbsync changes?
      5. We should gracefully stop all processes in the context of a space; dbsync in/out streams, harvesting, import, autocleaning, file pop. etc

            plglopiola Łukasz Opioła
            plglopiola Łukasz Opioła
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: