Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-422 Replicated master process (no master SPOF)
  3. KUDU-495

Master should handle the case where we REPLICATE fails

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: M5, 0.7.0
    • Fix Version/s: 0.9.0
    • Component/s: master
    • Labels:
      None
    • Target Version/s:

      Description

      Master should handle the case where the REPLICATE fails (which I discovered when running a transaction against a non-leader case) in SysTables.

      This is a bit tricky as for master we update the in-memory tables first, then commit the transaction.

      Only way would be able to do the following:

      Under the lock for the appropriate CopyOnWrite object--

      1) Save the old version of the object.
      2) Make the appropriate modification.
      3) If REPLICATE fails, go back to the old version.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                adar Adar Dembo
                Reporter:
                avf Alex Feinberg
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: