Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-6469

config.changelog not integrated with locking in operations themselves

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Cannot Reproduce
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding

    Description

      ... resulting in changelog entries potentially being reordered in arbitrary ways over short time periods.

      It's difficult to create automated tools if we can't trust the changelog ordering - even small differences could result in failure. We can try to make our tools "guess", but this is A) hard to do in a portable way and B) won't ever be 100% correct.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: