kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3725) Update documentation with regards to XFS
Date Mon, 11 Jul 2016 00:29:10 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370023#comment-15370023

ASF GitHub Bot commented on KAFKA-3725:

GitHub user toddpalino opened a pull request:


    KAFKA-3725: Update documentation with regards to XFS

    I've updated the ops documentation with information on using the XFS filesystem, based
on LinkedIn's testing (and subsequent switch from EXT4).
    I've also added some information to clarify the potential risk to the suggested EXT4 options
(again, based on my experience with a multiple broker failure situation).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/toddpalino/kafka trunk

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1605
commit 9865bf0c50f7967d72fe8ae9f5a45bbdf96f4b5c
Author: tpalino <tpalino@linkedin.com>
Date:   2016-07-11T00:25:02Z

    Update ops docs with XFS information


> Update documentation with regards to XFS
> ----------------------------------------
>                 Key: KAFKA-3725
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3725
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Ismael Juma
>            Assignee: Todd Palino
> Our documentation currently states that only Ext4 has been tried (by LinkedIn):
> "Ext4 may or may not be the best filesystem for Kafka. Filesystems like XFS supposedly
handle locking during fsync better. We have only tried Ext4, though."
> http://kafka.apache.org/documentation.html#ext4
> I think this is no longer true, so we should update the documentation.

This message was sent by Atlassian JIRA

View raw message