Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-2157

1.5 -> 1.4 -> 1.5 downgrade/re-upgrade can result in non-startable tservers

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.4.0, 1.5.0, 1.6.0
    • Fix Version/s: 1.7.0
    • Component/s: fs, tserver
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tlipcon Todd Lipcon
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: