Tags: zhangyifan27/kudu
Tags
[kudu CLI] KUDU-2443 fix replica movement for RF=1 During replica replacement, if the leader replica is being replaced, do not ask it to step down until the newly added replica transitions into a voter role. Otherwise, that might prevent tablet copying to finish successfully under racy conditions in case of replication factor of 1. The workaround described above works OK for the case of moving/replacing replicas in the context of KUDU-2443. The core of the underlying issue will be addressed separately: see KUDU-2446 for details. This changelist also contains a small clean-up in tool_action_tablet.cc (the clean-up itself does not contain any functional changes). Change-Id: I59ce249ae4e3bbcf42d8d754c68d1b92ab93f287 Reviewed-on: http://gerrit.cloudera.org:8080/10439 Reviewed-by: Mike Percy <mpercy@apache.org> Tested-by: Kudu Jenkins (cherry picked from commit b73dec1) Reviewed-on: http://gerrit.cloudera.org:8080/10467 Reviewed-by: Grant Henke <granthenke@apache.org> Tested-by: Alexey Serbin <aserbin@cloudera.com>
Bump version to 1.7.1 (non-SNAPSHOT) Change-Id: I07a4fbe564a095c64ae12c48c7200d31aff610c7 Reviewed-on: http://gerrit.cloudera.org:8080/10280 Tested-by: Kudu Jenkins Reviewed-by: Todd Lipcon <todd@apache.org>
release notes: some edits - Some small wording improvements - Moved 3-4-3 replication to new features since it seems large enough to not just be an "improvement" - Added a note that the 3-disks-per-replica change only affects new replicas - Stopped documenting the experimental flag which goes back to 3-2-3 replication since we'd like to remove it in the future, and we don't know of any compelling reasons for someone to change it. - Moved KUDU-2259 to "fixed issues" since it was seen as a bug - Added a few explanations of the results of some fixes instead of the implementations. Change-Id: I944a302a7fe5c86d0204545157efb92407573e1e Reviewed-on: http://gerrit.cloudera.org:8080/9703 Reviewed-by: Alexey Serbin <aserbin@cloudera.com> Reviewed-by: Adar Dembo <adar@cloudera.com> Tested-by: Grant Henke <granthenke@apache.org> Reviewed-by: Grant Henke <granthenke@apache.org> (cherry picked from commit 02d9578) Reviewed-on: http://gerrit.cloudera.org:8080/9706
Bump version to 1.7.0 (non-SNAPSHOT) Change-Id: I7493cfe5df51d8ef3ba08ec3876e585a55058968 Reviewed-on: http://gerrit.cloudera.org:8080/9686 Tested-by: Grant Henke <granthenke@apache.org> Reviewed-by: Dan Burkert <danburkert@apache.org>
java: Exclude org.apache.kudu.hive from javadoc generation Without this entry, I get the following error when deploying: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (attach-javadocs) on project kudu-hive: MavenReportException: Error while generating Javadoc: [ERROR] Exit code: 1 - javadoc: error - No public or protected classes found to document. [ERROR] [ERROR] Command line was: /usr/lib/jvm/java-8-oracle/jre/../bin/javadoc -J-Xmx2048m @options @packages Change-Id: I6c40bd59715df500f7a9b612aff86de8d20dfc23 Reviewed-on: http://gerrit.cloudera.org:8080/8742 Reviewed-by: Mike Percy <mpercy@apache.org> Tested-by: Mike Percy <mpercy@apache.org> (cherry picked from commit 47544fd95bb333eaac9d37c4b3f679dcd60f6d2a) Reviewed-on: http://gerrit.cloudera.org:8080/8743
KUDU-2131: switch to LIFO log container retrieval Currently, LBM selects available log container from available container queue using FIFO, given the intention to spread the load across all available containers. However, this may cause inefficiency especially in the case of tablet copy if there is a long available containers queue. One failed test case is copying tablet of size 26.81GB on a tablet server with 14 disks and 19199 containers (only 97 of them are full). In this case, there are too many containers involved, so that DownloadBlocks took longer that 3m, the default idle timeout for a tablet copy session, to commit the new blocks such that the session is terminated before DownloadWALs. This patch switches to LIFO for log container selection, so that finalized blocks will exhaust one container at a time. Thus, when batching disk synchronization for a groups of created blocks, the number of fsync() operations will be significant lower for tablet servers with plenty of available log containers. It also marks '--tablet_copy_idle_timeout_ms', the flag that controls the amount of time without activity before a tablet copy session expires, as a user facing flag. And renames it to '--tablet_copy_idle_timeout_sec'. Change-Id: I6eb0bc99422c293417b64e0b6e86c87a3d55e687 Reviewed-on: http://gerrit.cloudera.org:8080/7956 Tested-by: Kudu Jenkins Reviewed-by: Adar Dembo <adar@cloudera.com>
PreviousNext