[jira] [Created] (KUDU-3321) Kudu tablet metadata populated incorrectly when master catalog is copied

["Abhishek (Jira)" <ji...@apache.org>]

Abhishek created KUDU-3321:
------------------------------

             Summary: Kudu tablet metadata populated incorrectly when master catalog is copied
                 Key: KUDU-3321
                 URL: https://issues.apache.org/jira/browse/KUDU-3321
             Project: Kudu
          Issue Type: Bug
    Affects Versions: 1.10.0
            Reporter: Abhishek


While adding a new master, we noticed the command “kudu local_replica copy_from_remote” was creating the tablet metadata but preserving the data directory UUIDs of remote master in the metadata like the below:

 
{code:java}
}
15 {
  1: "2ab404ac946846e6b14371b94cb08e47"
}
16: 0
{code}
 {color:#172b4d}2ab404ac946846e6b14371b94cb08e47 is the data directory UUID of the remote master.{color}

This caused the new master to not startup as it could not find the required data directory. Although this was specific to one host on the cluster this was not a one time occurrence. Copied the master catalog multiple times from different masters and all resulted in the same issue.

We discovered the workaround would be to open the editor to the pbc file ({{kudu pbc edit}}) and close it without making any changes. This removes the remote master data directory UUID and upon starting the new master it will eventually update it with the correct data directory UUID.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)