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 2021/08/24 19:17:03 UTC
[kudu] branch master updated (7feceaa -> 87a03ec)
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 7feceaa [spark] KUDU-1921 Add ability to require authn/encryption
new 8f47992 [docker] clarify on {MASTER,TSERVER}_ARGS
new 87a03ec [doc] update list of Kudu design highlights
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:
docker/kudu-entrypoint.sh | 14 +++++++++----
docs/index.adoc | 51 ++++++++++++++++++++++++++++++-----------------
2 files changed, 43 insertions(+), 22 deletions(-)
[kudu] 01/02: [docker] clarify on {MASTER,TSERVER}_ARGS
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 8f47992bbd4436f645e98c3d67e21f24df03fcce
Author: Alexey Serbin <al...@apache.org>
AuthorDate: Fri Aug 20 16:37:20 2021 -0700
[docker] clarify on {MASTER,TSERVER}_ARGS
This patch clarifies on how DEFAULT_ARGS are combined with
MASTER_ARGS and TSERVER_ARGS to build an effective set of
arguments to run kudu-master and kudu-tserver correspondingly.
This patch doesn't contain any functional changes.
Change-Id: Ieaeb54ee9aa74b638678eecf16fd224cbdc449dc
Reviewed-on: http://gerrit.cloudera.org:8080/17803
Tested-by: Kudu Jenkins
Reviewed-by: Bankim Bhavsar <ba...@cloudera.com>
Reviewed-by: Andrew Wong <aw...@cloudera.com>
---
docker/kudu-entrypoint.sh | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/docker/kudu-entrypoint.sh b/docker/kudu-entrypoint.sh
index 21485db..09e4cb5 100755
--- a/docker/kudu-entrypoint.sh
+++ b/docker/kudu-entrypoint.sh
@@ -52,11 +52,17 @@ function print_help {
echo " must also be set."
echo " Defaults to the value of the FS_WAL_DIR environment variable."
echo "MASTER_ARGS:"
- echo " Defines the arguments passed to kudu-master."
- echo " Defaults to the value of the DEFAULT_ARGS environment variable."
+ echo " Defines custom arguments passed to kudu-master."
+ echo " Defaults to an empty set."
+ echo " kudu-master is run with the set of arguments built from"
+ echo " DEFAULT_ARGS appended by MASTER_ARGS, so Kudu flags in DEFAULT_ARGS"
+ echo " can be overridden by corresponding flags in MASTER_ARGS."
echo "TSERVER_ARGS:"
- echo " Defines the arguments passed to kudu-tserver."
- echo " Defaults to the value of the DEFAULT_ARGS environment variable."
+ echo " Defines custom arguments passed to kudu-tserver."
+ echo " Defaults to an empty set."
+ echo " kudu-tserver is run with the set of arguments built from"
+ echo " DEFAULT_ARGS appended by TSERVER_ARGS, so Kudu flags in DEFAULT_ARGS"
+ echo " can be overridden by corresponding flags in TSERVER_ARGS."
echo "DEFAULT_ARGS:"
echo " Defines a recommended base set of arguments."
}
[kudu] 02/02: [doc] update list of Kudu design highlights
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 87a03ec9c6eeaf815cc03354937fb8fb24a79610
Author: Alexey Serbin <al...@apache.org>
AuthorDate: Mon Aug 23 16:04:29 2021 -0700
[doc] update list of Kudu design highlights
This changelist updates the list of Kudu design highlights on the /docs
page of the official Apache Kudu website to reflect the following:
* integration with MapReduce was removed in Kudu 1.15 release
* new features have been added since the Kudu 1.0 release
Change-Id: I169c1ed5020276dcaa33363fce32ad7a2e7db920
Reviewed-on: http://gerrit.cloudera.org:8080/17805
Tested-by: Kudu Jenkins
Reviewed-by: Andrew Wong <aw...@cloudera.com>
---
docs/index.adoc | 51 +++++++++++++++++++++++++++++++++------------------
1 file changed, 33 insertions(+), 18 deletions(-)
diff --git a/docs/index.adoc b/docs/index.adoc
index f693b6e..15f5d76 100644
--- a/docs/index.adoc
+++ b/docs/index.adoc
@@ -27,33 +27,48 @@
:sectlinks:
:experimental:
-Kudu is a columnar storage manager developed for the Apache Hadoop platform. Kudu shares
-the common technical properties of Hadoop ecosystem applications: it runs on commodity
-hardware, is horizontally scalable, and supports highly available operation.
+Kudu is a distributed columnar storage engine optimized for OLAP workloads.
+Kudu runs on commodity hardware, is horizontally scalable, and supports highly
+available operation.
Kudu's design sets it apart. Some of Kudu's benefits include:
- Fast processing of OLAP workloads.
-- Integration with MapReduce, Spark and other Hadoop ecosystem components.
-- Tight integration with Apache Impala, making it a good, mutable alternative to
- using HDFS with Apache Parquet.
- Strong but flexible consistency model, allowing you to choose consistency
- requirements on a per-request basis, including the option for strict-serializable consistency.
+ requirements on a per-request basis, including the option for
+ strict-serializable consistency.
+- Structured data model.
- Strong performance for running sequential and random workloads simultaneously.
+- Tight integration with Apache Impala, making it a good, mutable alternative to
+ using HDFS with Apache Parquet.
+- Integration with Apache NiFi and Apache Spark.
+- Integration with Hive Metastore (HMS) and Apache Ranger to provide
+ fine-grain authorization and access control.
+- Authenticated and encrypted RPC communication.
+- High availability: Tablet Servers and Masters use the <<raft>>, which ensures
+ that as long as more than half the total number of tablet replicas is
+ available, the tablet is available for reads and writes. For instance,
+ if 2 out of 3 replicas (or 3 out of 5 replicas, etc.) are available,
+ the tablet is available. Reads can be serviced by read-only follower tablet
+ replicas, even in the event of a leader replica's failure.
+- Automatic fault detection and self-healing: to keep data highly available,
+ the system detects failed tablet replicas and re-replicates data from
+ available ones, so failed replicas are automatically replaced when enough
+ Tablet Servers are available in the cluster.
+- Location awareness (a.k.a. rack awareness) to keep the system available
+ in case of correlated failures and allowing Kudu clusters to span over
+ multiple availability zones.
+- Logical backup (full and incremental) and restore.
+- Multi-row transactions (only for INSERT/INSERT_IGNORE operations as of
+ Kudu 1.15 release).
- Easy to administer and manage.
-- High availability. Tablet Servers and Masters use the <<raft>>, which ensures that
- as long as more than half the total number of replicas is available, the tablet is available for
- reads and writes. For instance, if 2 out of 3 replicas or 3 out of 5 replicas are available, the tablet
- is available.
-+
-Reads can be serviced by read-only follower tablets, even in the event of a
-leader tablet failure.
-- Structured data model.
By combining all of these properties, Kudu targets support for families of
-applications that are difficult or impossible to implement on current generation
-Hadoop storage technologies. A few examples of applications for which Kudu is a great
-solution are:
+applications that are difficult or impossible to implement using Hadoop storage
+technologies, while it is compatible with most of the data processing
+frameworks in the Hadoop ecosystem.
+
+A few examples of applications for which Kudu is a great solution are:
* Reporting applications where newly-arrived data needs to be immediately available for end users
* Time-series applications that must simultaneously support: