You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kudu.apache.org by gr...@apache.org on 2019/04/24 18:33:04 UTC

[kudu] branch branch-1.9.x updated (7ec64d9 -> 250d086)

This is an automated email from the ASF dual-hosted git repository.

granthenke pushed a change to branch branch-1.9.x
in repository https://gitbox.apache.org/repos/asf/kudu.git.


    from 7ec64d9  known_issues: document fault tolerant scan memory issue
     new 1fecd62  [docs] KUDU-2395 Add nscd to requirements
     new f145fdf  add document for KUDU-2080
     new 250d086  [docs] Adjust latency and bandwidth limitations

The 3 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/installation.adoc |  4 ++++
 docs/known_issues.adoc | 12 ++++++++----
 2 files changed, 12 insertions(+), 4 deletions(-)


[kudu] 01/03: [docs] KUDU-2395 Add nscd to requirements

Posted by gr...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

granthenke pushed a commit to branch branch-1.9.x
in repository https://gitbox.apache.org/repos/asf/kudu.git

commit 1fecd62105f62ec56cc3033f63f7e73e94bffc4f
Author: Attila Bukor <ab...@apache.org>
AuthorDate: Tue Apr 23 22:28:52 2019 +0200

    [docs] KUDU-2395 Add nscd to requirements
    
    Change-Id: Iad4db28297c08739b048dc46e398f7ddca80df48
    Reviewed-on: http://gerrit.cloudera.org:8080/13084
    Reviewed-by: Adar Dembo <ad...@cloudera.com>
    Tested-by: Kudu Jenkins
    Reviewed-by: Andrew Wong <aw...@cloudera.com>
    Reviewed-by: Alexey Serbin <as...@cloudera.com>
    (cherry picked from commit 70c2992bfa6658636939d4952794de882eff1037)
    Reviewed-on: http://gerrit.cloudera.org:8080/13098
---
 docs/installation.adoc | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/installation.adoc b/docs/installation.adoc
index d61f69c..2f3e188 100644
--- a/docs/installation.adoc
+++ b/docs/installation.adoc
@@ -51,6 +51,10 @@ Linux::
       information.
     - ntp.
     - xfs or ext4 formatted drives.
+    - Although not a strict requirement, it's highly recommended to use `nscd`
+      to cache both DNS name resolution and static name resolution. See
+      link:troubleshooting.html#slow_dns_nscd[troubleshooting slow DNS lookups]
+      for more information.
 macOS::
     - OS X 10.10 Yosemite, OS X 10.11 El Capitan, macOS Sierra, or macOS High Sierra.
 Windows::


[kudu] 02/03: add document for KUDU-2080

Posted by gr...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

granthenke pushed a commit to branch branch-1.9.x
in repository https://gitbox.apache.org/repos/asf/kudu.git

commit f145fdf2c580072708119e3d55acde4f6a2d8421
Author: jhc <ih...@163.com>
AuthorDate: Mon Mar 18 10:50:50 2019 +0800

    add document for KUDU-2080
    
    Change-Id: I7a802a846ad5ec93ce4e0022ec279f1b4c6cc5db
    Reviewed-on: http://gerrit.cloudera.org:8080/12774
    Tested-by: Kudu Jenkins
    Reviewed-by: Grant Henke <gr...@apache.org>
    (cherry picked from commit 8b727489eb787f9d0667192bb1160ed64e2aa70b)
    Reviewed-on: http://gerrit.cloudera.org:8080/13099
    Tested-by: Grant Henke <gr...@apache.org>
    Reviewed-by: Alexey Serbin <as...@cloudera.com>
---
 docs/known_issues.adoc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/known_issues.adoc b/docs/known_issues.adoc
index 88e6ba5..3ab0f26 100644
--- a/docs/known_issues.adoc
+++ b/docs/known_issues.adoc
@@ -112,6 +112,8 @@
 * Multi-data-center/multi-availability-zone configurations with a network latency
   over 100ms and bandwidth under 10 Gbps are not well tested and therefore not recommended.
 
+* All masters must be started at the same time when the cluster is started for the very first time.
+
 == Server management
 
 * Production deployments should configure a least 4GB of memory for tablet servers,


[kudu] 03/03: [docs] Adjust latency and bandwidth limitations

Posted by gr...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

granthenke pushed a commit to branch branch-1.9.x
in repository https://gitbox.apache.org/repos/asf/kudu.git

commit 250d086b150c58bec2b58133a4fb8394d45d8fc0
Author: Grant Henke <gr...@apache.org>
AuthorDate: Tue Apr 9 13:43:37 2019 -0700

    [docs] Adjust latency and bandwidth limitations
    
    Adjusts the documentation for latency and bandwidth
    limitations to be a bit more conservative. Additionally,
    removes any reference to DC/AZ deployments given
    we are primarily concerned about latency and bandwidth
    as the concrete limitations.
    
    Change-Id: I42fe8a65779c3f5ad366403366e534fa28713a76
    Reviewed-on: http://gerrit.cloudera.org:8080/12970
    Reviewed-by: Will Berkeley <wd...@gmail.com>
    Tested-by: Grant Henke <gr...@apache.org>
    Reviewed-by: Alexey Serbin <as...@cloudera.com>
    Reviewed-by: Mike Percy <mp...@apache.org>
    (cherry picked from commit 55d2faed94077ced16b736ca5e499022b0aa4789)
    Reviewed-on: http://gerrit.cloudera.org:8080/13100
    Tested-by: Kudu Jenkins
---
 docs/known_issues.adoc | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/docs/known_issues.adoc b/docs/known_issues.adoc
index 3ab0f26..ad5ba5d 100644
--- a/docs/known_issues.adoc
+++ b/docs/known_issues.adoc
@@ -106,11 +106,13 @@
 
 * Rolling restart is not supported.
 
-* Multi-data-center/multi-availability-zone configurations require at least 3
-  locations to maintain availability.
+* Recommended maximum point-to-point latency within a Kudu cluster is 20 milliseconds.
 
-* Multi-data-center/multi-availability-zone configurations with a network latency
-  over 100ms and bandwidth under 10 Gbps are not well tested and therefore not recommended.
+* Recommended minimum point-to-point bandwidth within a Kudu cluster is 10 Gbps.
+
+* If you intend to use the location awareness feature to place tablet servers in
+  different locations, it is recommended to measure the bandwidth and latency between servers
+  to ensure they fit within the above guidelines.
 
 * All masters must be started at the same time when the cluster is started for the very first time.