You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kudu.apache.org by al...@apache.org on 2019/10/11 20:21:21 UTC
[kudu] branch master updated (06621af -> 4d66740)
This is an automated email from the ASF dual-hosted git repository.
alexey pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git.
from 06621af [build] Fix a bug for memory_gc-itest
new 2768c15 [clock] log on CombineClocks() status only via VLOG
new 4d66740 Update version to 1.12.0-SNAPSHOT
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/release_notes.adoc | 66 ++++++++++++++++----------------------
examples/java/java-example/pom.xml | 2 +-
src/kudu/clock/builtin_ntp.cc | 20 +++++-------
version.txt | 2 +-
4 files changed, 38 insertions(+), 52 deletions(-)
[kudu] 02/02: Update version to 1.12.0-SNAPSHOT
Posted by al...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
alexey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git
commit 4d667403e55b70de74557643af455ff21438bf70
Author: Alexey Serbin <al...@apache.org>
AuthorDate: Thu Oct 10 23:34:31 2019 -0700
Update version to 1.12.0-SNAPSHOT
Change-Id: Ifd7a8e1de46cc4ac548c57337326e3f25a6a2099
Reviewed-on: http://gerrit.cloudera.org:8080/14413
Tested-by: Alexey Serbin <as...@cloudera.com>
Reviewed-by: Grant Henke <gr...@apache.org>
---
docs/release_notes.adoc | 66 ++++++++++++++++----------------------
examples/java/java-example/pom.xml | 2 +-
version.txt | 2 +-
3 files changed, 30 insertions(+), 40 deletions(-)
diff --git a/docs/release_notes.adoc b/docs/release_notes.adoc
index 0c362fe..0190126 100644
--- a/docs/release_notes.adoc
+++ b/docs/release_notes.adoc
@@ -16,7 +16,7 @@
// under the License.
[[release_notes]]
-= Apache Kudu 1.11.0 Release Notes
+= Apache Kudu 1.12.0 Release Notes
:author: Kudu Team
:imagesdir: ./images
@@ -28,88 +28,79 @@
:sectlinks:
:experimental:
-[[rn_1.11.0_upgrade_notes]]
+[[rn_1.12.0_upgrade_notes]]
== Upgrade Notes
-* Flume 1.8+ requires Java 8 at runtime even though the Kudu Flume integration
- is Java 7 compatible. Flume 1.9 is the default dependency version as of
- Kudu 1.9.0.
-* Hadoop 3.0+ requires Java 8 at runtime even though the Kudu Hadoop integration
- is Java 7 compatible. Hadoop 3.2 is the default dependency version as of
- Kudu 1.9.0.
-
-[[rn_1.11.0_obsoletions]]
+[[rn_1.12.0_obsoletions]]
== Obsoletions
-[[rn_1.11.0_deprecations]]
+[[rn_1.12.0_deprecations]]
== Deprecations
-* Support for Java 7 has been deprecated since Kudu 1.5.0 and may be removed in
- the next major release.
-[[rn_1.11.0_new_features]]
+[[rn_1.12.0_new_features]]
== New features
-[[rn_1.11.0_improvements]]
+[[rn_1.12.0_improvements]]
== Optimizations and improvements
-[[rn_1.11.0_fixed_issues]]
+[[rn_1.12.0_fixed_issues]]
== Fixed Issues
-[[rn_1.11.0_wire_compatibility]]
+[[rn_1.12.0_wire_compatibility]]
== Wire Protocol compatibility
-Kudu 1.11.0 is wire-compatible with previous versions of Kudu:
+Kudu 1.12.0 is wire-compatible with previous versions of Kudu:
-* Kudu 1.11 clients may connect to servers running Kudu 1.0 or later. If the client uses
+* Kudu 1.12 clients may connect to servers running Kudu 1.0 or later. If the client uses
features that are not available on the target server, an error will be returned.
-* Rolling upgrade between Kudu 1.10 and Kudu 1.11 servers is believed to be possible
+* Rolling upgrade between Kudu 1.11 and Kudu 1.12 servers is believed to be possible
though has not been sufficiently tested. Users are encouraged to shut down all nodes
in the cluster, upgrade the software, and then restart the daemons on the new version.
-* Kudu 1.0 clients may connect to servers running Kudu 1.11 with the exception of the
+* Kudu 1.0 clients may connect to servers running Kudu 1.12 with the exception of the
below-mentioned restrictions regarding secure clusters.
The authentication features introduced in Kudu 1.3 place the following limitations
-on wire compatibility between Kudu 1.11 and versions earlier than 1.3:
+on wire compatibility between Kudu 1.12 and versions earlier than 1.3:
-* If a Kudu 1.11 cluster is configured with authentication or encryption set to "required",
+* If a Kudu 1.12 cluster is configured with authentication or encryption set to "required",
clients older than Kudu 1.3 will be unable to connect.
-* If a Kudu 1.11 cluster is configured with authentication and encryption set to "optional"
+* If a Kudu 1.12 cluster is configured with authentication and encryption set to "optional"
or "disabled", older clients will still be able to connect.
-[[rn_1.11.0_incompatible_changes]]
-== Incompatible Changes in Kudu 1.11.0
+[[rn_1.12.0_incompatible_changes]]
+== Incompatible Changes in Kudu 1.12.0
-[[rn_1.11.0_client_compatibility]]
+[[rn_1.12.0_client_compatibility]]
=== Client Library Compatibility
-* The Kudu 1.11 Java client library is API- and ABI-compatible with Kudu 1.10. Applications
- written against Kudu 1.10 will compile and run against the Kudu 1.11 client library and
+* The Kudu 1.12 Java client library is API- and ABI-compatible with Kudu 1.11. Applications
+ written against Kudu 1.11 will compile and run against the Kudu 1.12 client library and
vice-versa.
-* The Kudu 1.11 {cpp} client is API- and ABI-forward-compatible with Kudu 1.10.
- Applications written and compiled against the Kudu 1.10 client library will run without
- modification against the Kudu 1.11 client library. Applications written and compiled
- against the Kudu 1.11 client library will run without modification against the Kudu 1.10
+* The Kudu 1.12 {cpp} client is API- and ABI-forward-compatible with Kudu 1.11.
+ Applications written and compiled against the Kudu 1.11 client library will run without
+ modification against the Kudu 1.12 client library. Applications written and compiled
+ against the Kudu 1.12 client library will run without modification against the Kudu 1.11
client library.
-* The Kudu 1.11 Python client is API-compatible with Kudu 1.10. Applications
- written against Kudu 1.10 will continue to run against the Kudu 1.11 client
+* The Kudu 1.12 Python client is API-compatible with Kudu 1.11. Applications
+ written against Kudu 1.11 will continue to run against the Kudu 1.12 client
and vice-versa.
-[[rn_1.11.0_known_issues]]
+[[rn_1.12.0_known_issues]]
== Known Issues and Limitations
Please refer to the link:known_issues.html[Known Issues and Limitations] section of the
documentation.
-[[rn_1.11.0_contributors]]
+[[rn_1.12.0_contributors]]
== Contributors
[[resources_and_next_steps]]
@@ -128,4 +119,3 @@ For full installation details, see link:installation.html[Kudu Installation].
- link:quickstart.html[Kudu Quickstart]
- link:installation.html[Installing Kudu]
- link:configuration.html[Configuring Kudu]
-
diff --git a/examples/java/java-example/pom.xml b/examples/java/java-example/pom.xml
index 3bb02d3..04762dc 100644
--- a/examples/java/java-example/pom.xml
+++ b/examples/java/java-example/pom.xml
@@ -28,7 +28,7 @@
<name>Kudu Java Client Examples</name>
<properties>
- <kudu-version>1.10.0</kudu-version>
+ <kudu-version>1.11.0</kudu-version>
</properties>
<build>
diff --git a/version.txt b/version.txt
index 7ed9261..79cd2d3 100644
--- a/version.txt
+++ b/version.txt
@@ -1 +1 @@
-1.11.0-SNAPSHOT
+1.12.0-SNAPSHOT
[kudu] 01/02: [clock] log on CombineClocks() status only via VLOG
Posted by al...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
alexey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git
commit 2768c156186e3da9693ddeff78a8d3206827fb88
Author: Alexey Serbin <al...@apache.org>
AuthorDate: Fri Oct 11 10:06:06 2019 -0700
[clock] log on CombineClocks() status only via VLOG
The logs about the walltime-would-move-back outcome of
BuiltInNtp::CombineClocks() look a bit scary, but de facto they
are benign and of nothing irregular in case of jittery reference
servers. Let's output them as VLOG(1) messages. These should
eventually be gone once the proper clock selection algorithm is
implemented (see KUDU-2939 for details).
Change-Id: I77ba6ea37b0e94058eaab018ae4d66976f0482cd
Reviewed-on: http://gerrit.cloudera.org:8080/14416
Tested-by: Kudu Jenkins
Reviewed-by: Grant Henke <gr...@apache.org>
---
src/kudu/clock/builtin_ntp.cc | 20 ++++++++------------
1 file changed, 8 insertions(+), 12 deletions(-)
diff --git a/src/kudu/clock/builtin_ntp.cc b/src/kudu/clock/builtin_ntp.cc
index af1e93d..dd13581 100644
--- a/src/kudu/clock/builtin_ntp.cc
+++ b/src/kudu/clock/builtin_ntp.cc
@@ -919,9 +919,8 @@ void BuiltInNtp::RecordResponse(ServerState* from_server,
// dispersion of samples increasing as described in
// https://tools.ietf.org/html/rfc5905 A.5.2. clock_filter()
const auto s = CombineClocks();
- if (!s.ok()) {
- KLOG_EVERY_N_SECS(INFO, 60)
- << Substitute("combining reference clocks failed: $0", s.ToString());
+ if (!s.ok() && VLOG_IS_ON(1)) {
+ VLOG(1) << Substitute("combining clocks failed: $0", s.ToString());
}
}
@@ -1027,15 +1026,12 @@ Status BuiltInNtp::CombineClocks() {
// Extra sanity check to make sure walltime doesn't go back.
std::lock_guard<rw_spinlock> l(last_computed_lock_);
if (last_computed_.wall > compute_wall) {
- auto msg = Substitute("walltime would move into past: "
- "current walltime $0, last walltime $1, "
- "current mono $2, last mono $3, "
- "current error $4, last error $5",
- compute_wall, last_computed_.wall,
- now, last_computed_.mono,
- compute_error, last_computed_.error);
- VLOG(1) << msg;
- return Status::IllegalState(msg);
+ return Status::IllegalState(Substitute(
+ "walltime would move into past: "
+ "current walltime $0, last walltime $1, "
+ "current mono $2, last mono $3, current error $4, last error $5",
+ compute_wall, last_computed_.wall,
+ now, last_computed_.mono, compute_error, last_computed_.error));
}
last_computed_.is_synchronized = true;
last_computed_.mono = now;