kudu-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Dasch <jeff_da...@yahoo.com>
Subject Re: Feature request for Kudu 1.3.0
Date Fri, 10 Feb 2017 19:23:15 GMT
 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.

On Friday, February 10, 2017, 12:45 PM, Todd Lipcon <todd@cloudera.com> wrote:

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 partition between the two racks).
On Fri, Feb 10, 2017 at 7:27 AM, Jeff Dasch <jeff_dasch@yahoo.com> wrote:

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 Kerberos and TLS for some production systems, for my use-case
data availability really takes priority.
I looked at your scoping document, and for what it's worth, I'm fine with a shell script that
is similar to what Hadoop uses.

Todd Lipcon
Software Engineer, Cloudera

View raw message