About mfulwiler

mfulwiler · ‎04-04-2019

Thanks Hoa Hoa, for the reply I will test these steps out they seem pretty straight forwards thanks for you help. One thing I have a question about is step 2 you are stay to stop doing any DDL to the masters does this mean I should take down the other masters or make sure we dont have any DDL stametns running which may be a little tricky once we move to production.

mfulwiler · ‎04-03-2019

Hi all, We are going through the hassle of rebuilding our boxes with CentOS7 as there is no upgrade path from CentOS6. Now I have looked over these Kudu documentation to migrating to multiple kudu master but the problem is the first warning it says it is unsafe to do this so I guess my question would be can I take one master making it a 2 node master then follow the documentation on migrating to a 3 node master setup. what process would I follow to remove the 3rd master other than just deleteing the role as I can only imagine how kudu will handle this. Also we are running kudu 1.4

mfulwiler · ‎03-01-2019

Thanks again this seemed to have fixed the issue I am going through most of the tables as it looks like a few of them are still trying to talk to the old UUID.

mfulwiler · ‎02-28-2019

Thanks! This seemed to work for all but one tablet. When I run the command, I get the following message. Illegal state: RaftConfig change currently pending. Only one is allowed at a time. Committed config: opid_index: 920502 OBSOLETE_local: false peers { permanent_uuid: "13950e716d21404188b733521dbf4d97" member_type: VOTER last_known_addr { host: "node02.domain.com" port: 7050 } } peers { permanent_uuid: "fa6625fcbb204fba86ac6d4007c3f695" member_type: VOTER last_known_addr { host: "node10.domain.com" port: 7050 } } peers { permanent_uuid: "fe5c3538509d47d186f5784ea586f260" member_type: VOTER last_known_addr { host: "node12.researchnow.com" port: 7050 } }. Pending config: opid_index: 1318207 OBSOLETE_local: false peers { permanent_uuid: "13950e716d21404188b733521dbf4d97" member_type: VOTER last_known_addr { host: "node02.domain.com" port: 7050 } } peers { permanent_uuid: "fe5c3538509d47d186f5784ea586f260" member_type: VOTER last_known_addr { host: "node12.domain.com" port: 7050 } }

mfulwiler · ‎02-28-2019

Hello all, I seem to have run into a Kudu 1.4 bug, and I am wondering if there is any work around other than upgrading. I lost a tablet in my dev environment and wasn't aware of it for a while (24hours or so) which I just assumed I could just wipe the directories and rebuild it thinking all the replicas had already been replicated to other tablets well that wasn't the case. After getting the tablet backup I ran a ksck and noted I have two tables that are under-replicated, and I am seeing a lot of alerts like the one below. Now I did see this https://issues.apache.org/jira/browse/KUDU-1613 and it says it's fixed in 1.7 but upgrading isn't an option at this time. T acc6adcd6b554b5cabfed268184591a9 P fa6625fcbb204fba86ac6d4007c3f695 -> Peer 13950e716d21404188b733521dbf4d97 (1.2.3.4.domain.com:7050): Couldn't send request to peer 13950e716d21404188b733521dbf4d97 for tablet acc6adcd6b554b5cabfed268184591a9. Error code: WRONG_SERVER_UUID (16). Status: Invalid argument: UpdateConsensus: Wrong destination UUID requested. Local UUID: 71fc2ef6adb54e59b27de1ca1c8cbbf9. Requested UUID: 13950e716d21404188b733521dbf4d97. Retrying in the next heartbeat period. Already tried 354599 times.

Online	Offline
Last Visited	‎10-22-2019 12:01 PM

Member Since	‎04-26-2017 01:51 PM
Last Visited	‎10-22-2019 12:01 PM
Posts	16

Cloudera Community

Re: Migrate one of three kudu master to a new serv...

Migrate one of three kudu master to a new server

Re: Kudu Error code: WRONG_SERVER_UUID

Re: Kudu Error code: WRONG_SERVER_UUID

Kudu Error code: WRONG_SERVER_UUID