On Fri, Feb 10, 2017 at 10:32 AM, Weber, Richard <[email protected]> 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 install 1/3 of a region at a time. That means 1/3 > of the cluster can be down for the SW install, reboot, or something else. > Allowing rack locality to be logically defined will allow the data to still > be available during normal maintenance operations. > > That's an interesting use case. How long is the 1/3rd of the cluster typically down for? I'd be afraid that, if it's down for more than a couple minutes, there's a decent chance of losing one server in the other 2/3 region, which would leave a tablet at 1/3 replication and unavailable for writes or consistent reads. Is that acceptable for your target use cases? There are certain things we could consider doing to allow a replica to fall to 1/3 while still remaining online, but don't think we've considered doing them any time particularly soon. Would be good to get data on how important that is. -Todd > > > > > > > > -- Rick Weber > > > > > > *From: *Todd Lipcon <[email protected]> > *Reply-To: *"[email protected]" <[email protected]> > *Date: *Friday, February 10, 2017 at 12:45 PM > *To: *"[email protected]" <[email protected]> > *Subject: *Re: Feature request for Kudu 1.3.0 > > > > 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). > > > > -Todd > > > > On Fri, Feb 10, 2017 at 7:27 AM, Jeff Dasch <[email protected]> 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. > > > > thanks, > > -jeff > > > > > > > > > > > > -- > > Todd Lipcon > Software Engineer, Cloudera > -- Todd Lipcon Software Engineer, Cloudera
