[
https://issues.apache.org/jira/browse/KUDU-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335185#comment-16335185
]
Jeffrey F. Lukman commented on KUDU-2126:
-----------------------------------------
Pushed in
[7465c91b84656281535fa825a9befb6bee172a9d|https://github.com/apache/kudu/commit/7465c91b84656281535fa825a9befb6bee172a9d]
> DeleteTablet RPC on an already deleted tablet should be a no-op
> ---------------------------------------------------------------
>
> Key: KUDU-2126
> URL: https://issues.apache.org/jira/browse/KUDU-2126
> Project: Kudu
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.5.0
> Reporter: Adar Dembo
> Assignee: Jeffrey F. Lukman
> Priority: Major
> Labels: newbie
>
> This is remaining (but lower priority) work from KUDU-2114:
> bq. 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
