[
https://issues.apache.org/jira/browse/KUDU-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357488#comment-16357488
]
Todd Lipcon commented on KUDU-2290:
-----------------------------------
Just a tip on how this tool might be implemented: I think if we just got the
master to change the existing tablet to REPLACED state and inserted a new one
in CREATING state it would roll forward as if it was just in the process of
creating the table. Might be safer all around to use a new tablet ID rather
than try to create an empty tablet with the old ID. (just in case the
"permanently missing" tablet actually does come back from the dead)
> Tool to re-create a tablet
> --------------------------
>
> Key: KUDU-2290
> URL: https://issues.apache.org/jira/browse/KUDU-2290
> Project: Kudu
> Issue Type: New Feature
> Components: ops-tooling
> Reporter: Andrew Wong
> Priority: Major
>
> In cases where all replicas for single tablet become permanently unavailable,
> the entire table is affected. The solution today would be to drop the entire
> table and recreate it.
> Rather than doing this, it would be nice to have a tool to create stand-ins
> for the tablet (e.g. with the same schema, partitioning properties, etc.),
> with the understanding that existing data for that tablet has been lost
> forever. That way, users would at least be able to operate on the tables
> (albeit with some missing data).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
