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 C1240200D5D for ; Wed, 20 Dec 2017 20:30:54 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id BF99F160C15; Wed, 20 Dec 2017 19:30:54 +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 E02DA160BF9 for ; Wed, 20 Dec 2017 20:30:53 +0100 (CET) Received: (qmail 10775 invoked by uid 500); 20 Dec 2017 19:30:53 -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 10765 invoked by uid 99); 20 Dec 2017 19:30:53 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Dec 2017 19:30:53 +0000 Received: from mail-ot0-f169.google.com (mail-ot0-f169.google.com [74.125.82.169]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 33A421A00E8 for ; Wed, 20 Dec 2017 19:30:51 +0000 (UTC) Received: by mail-ot0-f169.google.com with SMTP id d27so20564037ote.11 for ; Wed, 20 Dec 2017 11:30:50 -0800 (PST) X-Gm-Message-State: AKGB3mKsZXW+DZERRvAbDD604zTW3U3kKjJZXwWRdPEx/bJcBCC3Ix9d FGEqXNiQYHcvUSHzHTnCUyCLB3Kmmb9DvsppNPXF4w== X-Google-Smtp-Source: ACJfBotQAc/xjtNp8wJy9OX+bR00PudtXuAU1mrm76gp9bi7RHCimENKA0yVGPlr0DQIBYqGJC8eciWdT+wXG61aPOk= X-Received: by 10.157.10.119 with SMTP id 110mr6332661otg.138.1513798250156; Wed, 20 Dec 2017 11:30:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.10.72 with HTTP; Wed, 20 Dec 2017 11:30:09 -0800 (PST) In-Reply-To: <692550816.1974794.1513768771297@mail.yahoo.com> References: <692550816.1974794.1513768771297.ref@mail.yahoo.com> <692550816.1974794.1513768771297@mail.yahoo.com> From: Dan Burkert Date: Wed, 20 Dec 2017 11:30:09 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Kudu Queries To: user@kudu.apache.org Content-Type: multipart/alternative; boundary="001a113ed0d6f683180560ca9e46" archived-at: Wed, 20 Dec 2017 19:30:54 -0000 --001a113ed0d6f683180560ca9e46 Content-Type: text/plain; charset="UTF-8" Hi Ajay, Have you looked at the documentation section on kudu.apache.org? In particular these sections may be helpful: https://kudu.apache.org/docs/schema_design.html https://kudu.apache.org/docs/administration.html#migrate_to_multi_master https://kudu.apache.org/docs/administration.html#_adding_a_data_directory Answers to specific questions inline: On Wed, Dec 20, 2017 at 3:19 AM, ajay chaudhary wrote: we would want to know how would insert be handled when one of the node is > 100% full for some reason. > As inserts are attempted, the tablets on that server will begin to fail and be re-replicated to other tservers. This can cause a cascading scenario, so you should avoid running with full disks. How can we add a node to Kudu Cluster? what is the process. > Just stand up the tablet server process and point it to the existing master. > Can we add a node to Kudu cluster and exisiting tables can make use of it > automatically ? or is there any process around it? > Kudu won't rebalance automatically to the new server. If you create new tables, or if tablets of existing tables failover and are re-replicated, then the new tablet servers will be considered as destinations for the new tablets. The move-replica tool is available to manually move tablets around, but it's somewhat difficult to use for large coordinated re-balancing, hopefully we'll grow some better tools here soon. > Can we add/delete more partition(hash) to exisiting kudu tables? > No, only range partitions can be added or removed. --001a113ed0d6f683180560ca9e46 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Answers to specific questions inline:
=
On Wed, Dec 20, 2017 at 3:19 AM, ajay chaudh= ary <juniorajay@yahoo.com> wrote:

we would want to know how= =20 would insert be handled when one of the node is 100% full for some=20 reason.

As inserts are attempted, the tablets on that server will begin = to fail and be re-replicated to other tservers. This can cause a cascading = scenario, so you should avoid running with full disks.

<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">
How can= we add a node to Kudu Cluster? what is the process.
=

Just stand up the tablet server process an= d point it to the existing master.
=C2=A0
Can we add a node to= Kudu cluster and exisiting tables can make use of it automatically ? or is= there any process around it?

=
Kudu won't rebalance automatically to the new server. If you=20 create new tables, or if tablets of existing tables failover and are re-rep= licated, then=20 the new tablet servers will be considered as destinations for the new=20 tablets.=C2=A0 The move-replica tool is available to manually move tablets around, but it's somewhat= =20 difficult to use for large coordinated re-balancing, hopefully we'll=20 grow some better tools here soon.
=C2=A0
Can we add/delete more = partition(hash) to exisiting kudu tables?

No, only range partitions can be added or removed.
<= /div>

--001a113ed0d6f683180560ca9e46--