Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.89.20100924
    • Component/s: None
    • Labels:
      None

      Description

      Atomicity can be achieved in two ways – by using a multiversion concurrency system (MVCC), or (ii) by ensuring that "new" writes do not complete, until the "old" reads complete.

      Currently, Memstore uses something along the lines of MVCC (called RWCC for read-write-consistency-control). But, this mechanism is not incorporated for the key-values written to the disk, as they do not include the memstore TS.

      Let us make the two approaches be similar, by persisting the memstoreTS along with the key-value when it is written to the disk.

        Attachments

        1. 4344-v12.txt
          39 kB
          Amitanand Aiyer
        2. 4344-v11.txt
          30 kB
          Ted Yu
        3. 4344-v10.txt
          29 kB
          Amitanand Aiyer
        4. 4344-v9.txt
          30 kB
          Ted Yu
        5. 4344-v8.txt
          30 kB
          Amitanand Aiyer
        6. 4344-v7.txt
          31 kB
          Ted Yu
        7. 4344-v6.txt
          32 kB
          Ted Yu
        8. 4344-v5.txt
          31 kB
          Ted Yu
        9. 4344-v4.txt
          30 kB
          Lars Hofhansl
        10. 4344-v2.txt
          21 kB
          Ted Yu
        11. patch-2
          26 kB
          Amitanand Aiyer

          Activity

            People

            • Assignee:
              amitanand Amitanand Aiyer
              Reporter:
              amitanand Amitanand Aiyer
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: