I'm headed out of town on Fri but here are some release notes for the features/improvements I worked on:
Improvements: - Tablet server startup time has been improved significantly on servers containing large numbers of blocks. - Various optimizations were made to reduce the 99th percentile latency of writes on the tablet server. This can also improve throughput on certain write workloads, particularly on larger clusters. - (KUDU-2198) Kudu may now be configured to ignore system-wide auth_to_local mappings configured in /etc/krb5.conf by setting the `use_system_auth_to_local` flag to `false`. - The performance of the compaction scheduler has been improved. In previous versions, certain types of time series workloads were found to cause compaction scheduling to take tens of seconds. These workloads now schedule compactions an order of magnitude more efficiently. - The compaction scheduler has been improved to avoid running a compaction when the benefit of that compaction is extremely small. - Kudu servers can now tolerate short interruptions in NTP clock synchronization. NTP synchronization is still required when any Kudu daemon starts up. If NTP synchronization is not available, diagnostic information is now logged to help pinpoint the issue. (KUDU-1578) - Tablet servers now consider the health of all replicas of a tablet before deciding to evict one. This can improve stability of the Kudu cluster after experiencing multiple simultaneous daemon failures (KUDU-2048). - Several performance improvements have been made to the Kudu master, particularly in concurrency of clients opening tables. This should improve performance in highly concurrent workloads. Bug fixes: - KUDU-1078: fixed an error message commonly found in tablet server logs indicating that operations were being read "from the future". -Todd On Wed, Nov 22, 2017 at 12:32 PM, Mike Percy <[email protected]> wrote: > Thanks all for your responses and support of this plan. Today I'll post a > patch for a "blank" 1.6 release notes document, which folks can start > adding their release notes to. I'll pick up the slack on whatever hasn't > yet been documented when I branch next week (and I might ping people > individually to ask for their help documenting the changes they worked on). > > Mike > > On Mon, Nov 20, 2017 at 11:30 AM, Hao Hao <[email protected]> wrote: > > > +1, thanks Mike for volunteering! > > > > Best, > > Hao > > > > On Mon, Nov 20, 2017 at 10:43 AM, Todd Lipcon <[email protected]> wrote: > > > > > Sounds good to me. Thanks for volunteering, Mike. > > > > > > -Todd > > > > > > On Fri, Nov 17, 2017 at 9:37 PM, Alexey Serbin <[email protected]> > > > wrote: > > > > > > > Hi Mike, > > > > > > > > Thank you for taking care of the process for 1.6.0 release. > > > > The plan you described looks good to me. > > > > > > > > > > > > Best regards, > > > > > > > > Alexey > > > > > > > > > > > > On 11/16/17 1:51 AM, Mike Percy wrote: > > > > > > > >> Hi Kudu dev community, > > > >> > > > >> It's been 2 months since release 1.5.0 and we've got a bunch of > > valuable > > > >> improvements and bug fixes waiting in the wings. Based on our usual > > > >> 2-month > > > >> cadence, now looks like a good time to start thinking about a Kudu > > 1.6.0 > > > >> release. > > > >> > > > >> I'll volunteer to RM this one, unless someone else has a burning > > desire > > > to > > > >> do it. > > > >> > > > >> I'll also propose to cut the branch for 1.6.x early in the week > > *after* > > > >> the > > > >> Thanksgiving holiday in the US, and to start a vote on RC1 a couple > of > > > >> days > > > >> after that. > > > >> > > > >> Devs: That means release notes for notable changes in 1.6 should be > up > > > for > > > >> review and ready to go by Monday, November 27 (the Monday after > > > >> Thanksgiving) to ensure their inclusion. > > > >> > > > >> Please let me know your thoughts on the above plan. > > > >> > > > >> Thanks! > > > >> Mike > > > >> > > > >> > > > > > > > > > > > > > -- > > > Todd Lipcon > > > Software Engineer, Cloudera > > > > > > -- Todd Lipcon Software Engineer, Cloudera
