Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.11
    • Component/s: mongomk
    • Labels:
      None

      Description

      The current MongoMK implementation has some disadvantages we would like to address:

      • some of the collections can't be sharded easily
      • instances synchronize on the "sync" collection
      • concurrent changes to the same node are detected relatively late,
        and merging them requires a re-try

      To address those issues, we will write a prototype of a MongoMK implementation that uses a different storage model, that is, only one "nodes" collection.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Thomas Mueller
            Reporter:
            Thomas Mueller
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development