[1/2] kudu git commit: Factor out consensus queue methods

Repository: kudu Updated Branches: refs/heads/master a74f9a0dc -> f2479e21d Factor out consensus queue methods This patch factors a couple of code blocks out into methods to reduce the line count of PeerMessageQueue::ResponseFromPeer(). Change-Id: I278de150e3dc42181ccfbbd3a4c0e5cc4de90c1a Rev

[2/2] kudu git commit: KUDU-2342. consensus: use tighter bound for non-voter promotion

KUDU-2342. consensus: use tighter bound for non-voter promotion This patch replaces the NON_VOTER promotion heuristic based on the --consensus_promotion_max_wal_entries_behind gflag with a heuristic that roughly matches the promotion criteria outlined in Diego Ongaro's dissertation. The approach

kudu git commit: [consensus] FAILED_UNRECOVERABLE replica health status

Repository: kudu Updated Branches: refs/heads/master e684de337 -> a74f9a0dc [consensus] FAILED_UNRECOVERABLE replica health status Added HealthStatus::FAILED_UNRECOVERABLE for a tablet replica. This is to mark replicas which are not able to catch up with the leader due to GC-collected segments

kudu git commit: KUDU-2259: add real user to AuthenticationCredentialsPB

Repository: kudu Updated Branches: refs/heads/branch-1.7.x 132da394d -> c243d68be KUDU-2259: add real user to AuthenticationCredentialsPB This commit adds the 'real user' to the authn credentials token, which is used when negotiating connections with SASL PLAIN authentication. This is useful w

kudu git commit: KUDU-2259: add real user to AuthenticationCredentialsPB

Repository: kudu Updated Branches: refs/heads/master 30cf90028 -> e684de337 KUDU-2259: add real user to AuthenticationCredentialsPB This commit adds the 'real user' to the authn credentials token, which is used when negotiating connections with SASL PLAIN authentication. This is useful when sc

kudu git commit: KUDU-2343. java: properly reconnect to new leader master after failover

Repository: kudu Updated Branches: refs/heads/branch-1.5.x 8c9dcc0ee -> 011a70b91 KUDU-2343. java: properly reconnect to new leader master after failover This fixes the "fake" location information returned in response to a ConnectToMaster RPC to include a distinct "fake UUID" for each master.

[1/2] kudu git commit: KUDU-1704: add python client support for READ_YOUR_WRITES mode

Repository: kudu Updated Branches: refs/heads/master 84244461d -> 30cf90028 KUDU-1704: add python client support for READ_YOUR_WRITES mode This patch allows users to specify READ_YOUR_WRITES as a read mode in python client. It adds correponding tests to ensure the mode is actually working. Ch

[3/3] kudu git commit: [release notes]: update notes for RYW read mode

[release notes]: update notes for RYW read mode Change-Id: I0bc5ae8452634a015891064bab5249eed6badf3e Reviewed-on: http://gerrit.cloudera.org:8080/9640 Tested-by: Hao Hao Reviewed-by: Grant Henke Project: http://git-wip-us.apache.org/repos/asf/kudu/repo Commit: http://git-wip-us.apache.org/repo

[2/3] kudu git commit: KUDU-1704: add python client support for READ_YOUR_WRITES mode

KUDU-1704: add python client support for READ_YOUR_WRITES mode This patch allows users to specify READ_YOUR_WRITES as a read mode in python client. It adds correponding tests to ensure the mode is actually working. Change-Id: I281a73ead2d606e698ff7f44ddb2cd1c78ffdd2a Reviewed-on: http://gerrit.cl

[1/3] kudu git commit: KUDU-2153. Servers should not delete tmp files until after locking directories

Repository: kudu Updated Branches: refs/heads/branch-1.7.x 9f4b70f89 -> 132da394d KUDU-2153. Servers should not delete tmp files until after locking directories This changes the order of FsManager startup to not try to clean tmp files until after successfully locking the data directories. This

[2/2] kudu git commit: [release notes]: update notes for RYW read mode

[release notes]: update notes for RYW read mode Change-Id: I0bc5ae8452634a015891064bab5249eed6badf3e Reviewed-on: http://gerrit.cloudera.org:8080/9634 Tested-by: Hao Hao Reviewed-by: David Ribeiro Alves Project: http://git-wip-us.apache.org/repos/asf/kudu/repo Commit: http://git-wip-us.apache.

kudu git commit: [release_notes] replica management scheme notes

Repository: kudu Updated Branches: refs/heads/branch-1.7.x 29d86fc83 -> 9f4b70f89 [release_notes] replica management scheme notes Added relevant notes on the new replica management scheme used in Kudu 1.7 by default: * the new replica management scheme is incompatible with old one * rollin

[1/2] kudu git commit: Update version to 1.8.0-SNAPSHOT

Repository: kudu Updated Branches: refs/heads/master 4c2bb92f1 -> 84244461d Update version to 1.8.0-SNAPSHOT Change-Id: I6552ec90cab4de52a88b1d3df7170ec6f3623140 Reviewed-on: http://gerrit.cloudera.org:8080/9628 Reviewed-by: Todd Lipcon Tested-by: Todd Lipcon Project: http://git-wip-us.apa

[2/2] kudu git commit: [release_notes] replica management scheme notes

[release_notes] replica management scheme notes Added relevant notes on the new replica management scheme used in Kudu 1.7 by default: * the new replica management scheme is incompatible with old one * rolling upgrade 1.6 -> 1.7 is not possible Change-Id: I49f1f1e17cdaee272592d598431a33dbfe55

kudu git commit: KUDU-2343. java: properly reconnect to new leader master after failover

Repository: kudu Updated Branches: refs/heads/branch-1.6.x 3aa933191 -> f8ae5117b KUDU-2343. java: properly reconnect to new leader master after failover This fixes the "fake" location information returned in response to a ConnectToMaster RPC to include a distinct "fake UUID" for each master.