[
https://issues.apache.org/jira/browse/ACCUMULO-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848000#comment-13848000
]
Mike Drob commented on ACCUMULO-2012:
-------------------------------------
Cloning the !METADATA table involves writes to the !METADATA table, to know
where the new tablets are, and those changes can't be reflected in the clone.
Cloning the root table might be easier, since while that also involves changes
to the !METADATA table, I don't think it will necessarily propagate into
changes on the original root table.
> Cloning the metadata table fails with faulty error
> --------------------------------------------------
>
> Key: ACCUMULO-2012
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2012
> Project: Accumulo
> Issue Type: Bug
> Components: client, master
> Reporter: John Vines
> Fix For: 1.6.0
>
>
> {code}
> Failed to execute Repo, tid=5d7e9a01796a6b64
> java.lang.RuntimeException: table deleted during clone? srcTableId =
> !0
> at
> org.apache.accumulo.server.util.MetadataTableUtil.initializeClone(MetadataTableUtil.java:681)
> at
> org.apache.accumulo.server.util.MetadataTableUtil.cloneTable(MetadataTableUtil.java:783)
> at
> org.apache.accumulo.master.tableOps.CloneMetadata.call(CloneTable.java:119)
> at
> org.apache.accumulo.master.tableOps.CloneMetadata.call(CloneTable.java:97)
> at
> org.apache.accumulo.master.tableOps.TraceRepo.call(TraceRepo.java:54)
> at
> org.apache.accumulo.fate.Fate$TransactionRunner.run(Fate.java:67)
> at
> org.apache.accumulo.fate.util.LoggingRunnable.run(LoggingRunnable.java:34)
> at java.lang.Thread.run(Thread.java:701)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
