Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 215CD200C32 for ; Thu, 9 Mar 2017 20:05:37 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1FD7D160B75; Thu, 9 Mar 2017 19:05:37 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4BA0B160B5F for ; Thu, 9 Mar 2017 20:05:29 +0100 (CET) Received: (qmail 51155 invoked by uid 500); 9 Mar 2017 19:05:28 -0000 Mailing-List: contact user-help@kudu.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@kudu.apache.org Delivered-To: mailing list user@kudu.apache.org Received: (qmail 51135 invoked by uid 99); 9 Mar 2017 19:05:28 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Mar 2017 19:05:28 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id AD29AC20E1 for ; Thu, 9 Mar 2017 19:05:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.152 X-Spam-Level: *** X-Spam-Status: No, score=3.152 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_NEUTRAL=0.652, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=onfocus-io.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id DAD5ERBXXs7j for ; Thu, 9 Mar 2017 19:05:25 +0000 (UTC) Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 5932D60FBA for ; Thu, 9 Mar 2017 19:05:25 +0000 (UTC) Received: by mail-io0-f181.google.com with SMTP id g6so34638506ioj.1 for ; Thu, 09 Mar 2017 11:05:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=onfocus-io.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=JYIzxzCZyug/5wEuBF56KK95rUEsJzis1hbxsTMQfts=; b=NckCCuPg5wT4V158KEnLMeau29wra5Owd9c7THSEnfNP63rkKiGhjFU7Omho7Dyj+d dvyPvEbp6EMuVHW+ZX1kLvUXvzCczFCedcsD2WvGnl8owJ1zkRLXCs8n+HgNF9CItRsG 3Z99Kmp/U2MUB6biv11tSLNLHNknx78tIVW2q2XiV3R5Omh9S/3X5TsGNkK+VX5GN5Zf IOh95tQc9wGZ2dQsP8G2puwM75sU/js7g8/of3vzWwTP1qjBlrs/s9VBbUY/x/dGbYSV MvcU6Yp5v+vZGmMy7NnpvGQwu2oSyfHcJUBOWHR5+2D97GzHjfToZXVg8j1O2yUuSNRP yWIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=JYIzxzCZyug/5wEuBF56KK95rUEsJzis1hbxsTMQfts=; b=lqnGm6PaL1k1ORxU66yurPacv7FdY7mUOubvrleI2/oJNySIhaNnVXFJ3e2ixzKGjo qf+uKJfhmX5e9W/asCwHSmoSCVvIer0sDoAWN/S3DPt246RU7qzjhis8D3+DBGKpuEQe JobUD5ct0JSXFHSa+QFSOb4rVLfoMTMgtiwQUcn7XPjLbG5Sqp7hEqREOLMdsfgCK6lG cNvyDyRImN5Hrc0IZm5fF5cTYoVn/ieoqnOYLQgWXRPdgrqZHwacK4WlexGG0XTq5JTv iv2roi/duxIKTjb/osMQTsQUuf917x8fK71sh7/gIaMmqnQJLlorzZzt/cOR7gKU6EoV Gabg== X-Gm-Message-State: AMke39l/zGpMebcMIG0SrexzXPo1hbti9XJU7GZkVwpw/3orbeXeFu24DrH/hZd92bMxOx04+jY1vrea+Joq+Q== X-Received: by 10.107.178.137 with SMTP id b131mr12050060iof.50.1489086324562; Thu, 09 Mar 2017 11:05:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.136.100 with HTTP; Thu, 9 Mar 2017 11:05:24 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Alexandre_Fouch=C3=A9?= Date: Thu, 9 Mar 2017 20:05:24 +0100 Message-ID: Subject: Re: How to reuse tablet server UUID, or removing old one To: user@kudu.apache.org Content-Type: multipart/alternative; boundary=001a114c98b46a8b08054a50ed5a archived-at: Thu, 09 Mar 2017 19:05:37 -0000 --001a114c98b46a8b08054a50ed5a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Oh ok, so since i need to do replace partitionning on all other nodes, i suppose tabletserver5 will get populated when i delete other tabletservers one by one. And indeed, now i see from the webUI, that all my tablets still have 3 replicas, so Kudu must have ensured a replication of 3 when tabletserver5 was considered dead. (i wonder how much time after though) Yet, is it possible to have the masters forget about the dead tablet server UUID, so that it does not show up anymore in the webUI ? Or will it disapperar after a while or a Kudu restart maybe ? 2017-03-09 17:48 GMT+01:00 Jean-Daniel Cryans : > Hi Alexandre, > > Tablet replicas are not tied to a UUID, so removing or reusing one > wouldn't achieve what you want. The main thing missing here is that Kudu > doesn't do tablet re-balancing at runtime, so tabletserver5 will get > tablets the next time a node dies or if you create new tables. > > Obviously that's something we'd like to address but nobody has come aroun= d > to doing it so far. > > Sinc=C3=A8rement, > > J-D > > On Thu, Mar 9, 2017 at 6:34 AM, Alexandre Fouch=C3=A9 > wrote: > >> Hi all >> >> I have searched and searched, but could not find how to tell that a >> previous tablet server uuid is to be removed >> I had to replace disks on tabletserver5, so i deleted all data, since >> there were replicas on other servers. Now that i restarted Kudu on >> tabletserver5 with empty data, it initialised fine, but since (i saw >> afterwards on webUI) it has a new UUID, it is recognised as a new server= , >> and it does not resync its tablets replcas with other tablet servers >> (edited). It has the same hostname as before but different UUID >> >> And in WebUI, i see the same tabletserver5 with the previous UUID marked >> as =E2=80=98dead' >> >> How can i tel Kudu to completely remove the dead tabletserver5 UUID and >> populate the new tabletserver5 UUID instead ? >> >> the `kudu` command line tool does not seem to allow to delete a tablet >> server UUID, or decommission >> so how ? >> >> Or other way, how can i recreate an empty Kudu tablet server reusing my >> old UUID ? >> > > --001a114c98b46a8b08054a50ed5a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Oh ok, so since i need to do replace partitionni= ng on all other nodes, i suppose tabletserver5 will get populated when i de= lete other tabletservers one by one.

And indeed, now i see fro= m the webUI, that all my tablets still have 3 replicas, so Kudu must have e= nsured a replication of 3 when tabletserver5 was considered dead. (i wonder= how much time after though)

Yet, is it possible to have the m= asters forget about the dead tablet server UUID, so that it does not show u= p anymore in the webUI ? Or will it disapperar after a while or a Kudu rest= art maybe ?


2017-03-09 17:48 GMT+01:00 Jean-Daniel Cryans <= ;jdcryans@apache.o= rg>:
Hi Al= exandre,

Tablet replicas are not tied to a UUID, so remo= ving or reusing one wouldn't achieve what you want. The main thing miss= ing here is that Kudu doesn't do tablet re-balancing at runtime, so tab= letserver5 will get tablets the next time a node dies or if you create new = tables.

Obviously that's something we'd li= ke to address but nobody has come around to doing it so far.

=
Sinc=C3=A8rement,

J-D

On Thu, Mar 9, 2017 at 6:34 AM, Alexandre Fouch=C3=A9 <a= fouche@onfocus.io> wrote:
<= div dir=3D"ltr">Hi all

I have searched and searched, but could not f= ind how to tell that a previous tablet server uuid is to be removed
I ha= d to replace disks on tabletserver5, so i deleted all data, since there wer= e replicas on other servers. Now that i restarted Kudu on tabletserver5 wit= h empty data, it initialised fine, but since (i saw afterwards on webUI) it= has a new UUID, it is recognised as a new server, and it does not resync i= ts tablets replcas with other tablet servers (edited). It has the same host= name as before but different UUID

And in WebUI, i see the same table= tserver5 with the previous UUID marked as =E2=80=98dead'

How can= i tel Kudu to completely remove the dead tabletserver5 UUID and populate t= he new tabletserver5 UUID instead ?

the `kudu` command line tool doe= s not seem to allow to delete a tablet server UUID, or decommission
so h= ow ?

Or other way, how can i recreate an empty Kudu tablet server re= using my old UUID ?


--001a114c98b46a8b08054a50ed5a--