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

implement "j" flag in write concern apply to secondary as well as primary

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Epic Link:
    • Sprint:
      Repl F (01/29/16), Repl 10 (02/19/16)
    • Linked BF Score:
      0

      Attachments

        Issue Links

        is duplicated by

        Bug - A problem which impairs or prevents the functions of the product. SERVER-22562 Protocol Version 1 causes very very slow chunk migrations

        • Major - P3 - Major loss of function.
        • Closed
        is related to

        Bug - A problem which impairs or prevents the functions of the product. SERVER-23956 Inconsistent behavior between 3.2.6-rc0 and 3.3.5 for writeconcern majority and journaling

        • Major - P3 - Major loss of function.
        • Closed

        Improvement - An improvement or enhancement to an existing feature or task. DOCS-7138 Describe new journal behavior in replication

        • Critical - P2 - Crashes, loss of data, severe memory leak.
        • Closed

        Improvement - An improvement or enhancement to an existing feature or task. SERVER-22337 Report lastAppliedAndJournaledOptime in replSetGetStatus

        • Major - P3 - Major loss of function.
        • Closed

        Improvement - An improvement or enhancement to an existing feature or task. SERVER-22488 Improve test coverage of new writeConcern j:true behavior

        • Major - P3 - Major loss of function.
        • Closed
        related to

        Bug - A problem which impairs or prevents the functions of the product. SERVER-22495 Running without journaling doesn't set all OpTimes (lastDurableOpTime)

        • Critical - P2 - Crashes, loss of data, severe memory leak.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. SERVER-22728 if journaling is disabled, update durableOpTime when appliedOpTime updates

        • Critical - P2 - Crashes, loss of data, severe memory leak.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. SERVER-22534 Change ephemeral storage to update durable OpTime

        • Major - P3 - Major loss of function.
        • Closed

        Task - A task that needs to be done. SERVER-22233 Reduce the secondary throttling during chunk migration

        • Major - P3 - Major loss of function.
        • Closed

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: