[
https://issues.apache.org/jira/browse/KUDU-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174209#comment-16174209
]
Todd Lipcon commented on KUDU-2157:
-----------------------------------
An ugly but effective workaround is:
{code}
find /data/ts-data/tablet-meta/* | EDITOR=/bin/touch xargs -n1 -P8
./KUDU-1.4.0-1.cdh5.12.1.p0.10/bin/kudu pbc edit
rm -f /data/ts-data/tablet-meta/*.bak.*
{code}
(running them through 'pbc edit' ends up dropping unknown fields, since our
ToJSON support doesn't write them out).
> 1.5 -> 1.4 -> 1.5 downgrade/re-upgrade can result in non-startable tservers
> ---------------------------------------------------------------------------
>
> Key: KUDU-2157
> URL: https://issues.apache.org/jira/browse/KUDU-2157
> Project: Kudu
> Issue Type: Bug
> Components: fs, tserver
> Affects Versions: 1.4.0, 1.5.0
> Reporter: Todd Lipcon
>
> I had a cluster running 1.5, which I then downgraded to 1.4 and ran for a
> while (including tablet copies happening). I then upgraded back to 1.5, but
> the tservers would not start.
> The issue is that the tablet-meta files on 1.5 had gotten invalid path IDs
> written into them during tablet copies that occurred on 1.4. The 1.4 servers
> had copied a remote TabletMeta file, and preserved the unknown protobuf field
> and serialized it locally. Then when we upgraded again, they failed to
> validate since they didn't match the local path UUIDs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
