Inline below as well.
On Fri, Feb 10, 2017 at 1:23 PM, Weber, Richard wrote:
>
>
>
> On Fri, Feb 10, 2017 at 10:32 AM, Weber, Richard
> wrote:
>
> I definitely would push for prioritization on this.
>
>
>
> Our main use case is less about multiple racks and failure, and more about
> functionali
Comments below
-- Rick Weber
From: Todd Lipcon
Reply-To: "user@kudu.apache.org"
Date: Friday, February 10, 2017 at 4:12 PM
To: "user@kudu.apache.org"
Subject: Re: Feature request for Kudu 1.3.0
On Fri, Feb 10, 2017 at 10:32 AM, Weber, Richard wrote:
I definitely would push fo
On Fri, Feb 10, 2017 at 10:32 AM, Weber, Richard wrote:
> I definitely would push for prioritization on this.
>
>
>
> Our main use case is less about multiple racks and failure, and more about
> functionality during the install process. Our clusters are installed in
> logical regions, and we ins
blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px
#715FFA solid !important; padding-left:1ex !important; background-color:white
!important; } Yup, more than two racks. Good to know about that partitioning
nuance. Thanks for considering the request.
-jeff
On Friday, F
I definitely would push for prioritization on this.
Our main use case is less about multiple racks and failure, and more about
functionality during the install process. Our clusters are installed in
logical regions, and we install 1/3 of a region at a time. That means 1/3 of
the cluster ca
Hi Jeff,
Thanks for the input on prioritization.
I'm curious: do you have more than two racks in your cluster? With Kudu's
replication strategy, we need at least three racks to be able to survive a
full rack outage. (with just two racks it's impossible to distinguish a
loss of a rack with a parti
blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px
#715FFA solid !important; padding-left:1ex !important; background-color:white
!important; } Any chance we can get a fix for KUDU-1535 "Add rack awareness"
added to the 1.3.0 release?
While I appreciate the need for Kerber
