You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Tom Bentley (Jira)" <ji...@apache.org> on 2020/02/25 12:05:00 UTC

[jira] [Resolved] (KAFKA-5554) Hilight config settings for particular common use cases

     [ https://issues.apache.org/jira/browse/KAFKA-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Bentley resolved KAFKA-5554.
--------------------------------
    Resolution: Abandoned

> Hilight config settings for particular common use cases
> -------------------------------------------------------
>
>                 Key: KAFKA-5554
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5554
>             Project: Kafka
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Tom Bentley
>            Assignee: Tom Bentley
>            Priority: Minor
>
> Judging by the sorts of questions seen on the mailling list, stack overflow etc it seems common for users to assume that Kafka will default to settings which won't lose messages. They start using Kafka and at some later time find messages have been lost.
> While it's not our fault if users don't read the documentation, there's a lot of configuration documentation to digest and it's easy for people to miss an important setting.
> Therefore, I'd like to suggest that in addition to the current configuration docs we add a short section highlighting those settings which pertain to common use cases, such as:
> * configs to avoid lost messages
> * configs for low latency
> I'm sure some users will continue to not read the documentation, but when they inevitably start asking questions it means people can respond with "have you configured everything as described here?"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)