Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-2126

DeleteTablet RPC on an already deleted tablet should be a no-op

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.5.0
    • Fix Version/s: 1.7.0
    • Component/s: tserver
    • Labels:

      Description

      This is remaining (but lower priority) work from KUDU-2114:

      When observed on a live cluster, it was further observed that the tablet deletion requests were rather expensive. It appears that a DeleteTablet RPC on a tombstone is not a no-op; it always flushes the superblock twice, which generates two fsyncs. This should also be addressed.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jeffreyflukman Jeffrey F. Lukman
                Reporter:
                adar Adar Dembo
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: