You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by jg...@apache.org on 2019/05/18 21:41:58 UTC

[kafka] branch trunk updated: MINOR: Fixed broken link to the IBM article about j-zerocopy (#6749)

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

jgus pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 51c72ad  MINOR: Fixed broken link to the IBM article about j-zerocopy (#6749)
51c72ad is described below

commit 51c72ad025bfaab9ee5035c9fd7ad6cf9d44b37c
Author: commandini <co...@users.noreply.github.com>
AuthorDate: Sat May 18 23:41:39 2019 +0200

    MINOR: Fixed broken link to the IBM article about j-zerocopy (#6749)
    
    Reviewers: Jason Gustafson <ja...@confluent.io>
---
 docs/design.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/design.html b/docs/design.html
index d389030..eadf29d 100644
--- a/docs/design.html
+++ b/docs/design.html
@@ -125,7 +125,7 @@
     <p>
     This combination of pagecache and sendfile means that on a Kafka cluster where the consumers are mostly caught up you will see no read activity on the disks whatsoever as they will be serving data entirely from cache.
     <p>
-    For more background on the sendfile and zero-copy support in Java, see this <a href="http://www.ibm.com/developerworks/linux/library/j-zerocopy">article</a>.
+    For more background on the sendfile and zero-copy support in Java, see this <a href="https://developer.ibm.com/articles/j-zerocopy/">article</a>.
 
     <h4><a id="design_compression" href="#design_compression">End-to-end Batch Compression</a></h4>
     <p>