[jira] [Updated] (KUDU-2157) 1.5 -> 1.4 -> 1.5 downgrade/re-upgrade can result in non-startable tservers

["Andrew Wong (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Wong updated KUDU-2157:
------------------------------
    Affects Version/s: 1.6.0

> 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, 1.6.0
>            Reporter: Todd Lipcon
>            Priority: Major
>             Fix For: 1.7.0
>
>
> 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
(v7.6.3#76005)