[2/3] kudu git commit: [consensus] update UnsafeChangeConfig() signature

2018-06-22 Thread danburkert
[consensus] update UnsafeChangeConfig() signature While testing various scenarios involving kudu CLI's 'remote_replica unsafe_change_config' sub-command, it turned out that tserver might end up trying to respond with invalid value of TabletServerErrorPB::Code. In that case, a tserver built in

[1/3] kudu git commit: KUDU-2260: Log block manager should handle null bytes in metadata on crash

2018-06-22 Thread danburkert
Repository: kudu Updated Branches: refs/heads/master c7918e87b -> f6e8fe6c6 KUDU-2260: Log block manager should handle null bytes in metadata on crash On ext4 with data=ordered (the default), it's possible for a write to persist an increase to the filesize without persisting the actual data.

[3/3] kudu git commit: Synchronizer::WaitFor thread-safety

2018-06-22 Thread danburkert
Synchronizer::WaitFor thread-safety WaitFor's implementation previously was not thread safe in the case that the waiter deallocated the Synchronizer after receiving a timeout. Change-Id: I9565a50839ffd23b5bac6986a6fdee41ac21aa3a Reviewed-on: http://gerrit.cloudera.org:8080/10783 Reviewed-by: