[
https://issues.apache.org/jira/browse/KAFKA-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262248#comment-14262248
]
Andrii Biletskyi edited comment on KAFKA-1786 at 1/23/15 12:05 PM:
-------------------------------------------------------------------
Created reviewboard https://reviews.apache.org/r/29513/diff/
against branch origin/trunk
UPD: discraded for now. Uploaded a patch KAFAK_1786.patch based on KAFKA-1845
(since it's a separate big patch)
was (Author: abiletskyi):
Created reviewboard https://reviews.apache.org/r/29513/diff/
against branch origin/trunk
> implement a global configuration feature for brokers
> ----------------------------------------------------
>
> Key: KAFKA-1786
> URL: https://issues.apache.org/jira/browse/KAFKA-1786
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Joe Stein
> Assignee: Andrii Biletskyi
> Fix For: 0.8.3
>
> Attachments: KAFKA_1786.patch
>
>
> Global level configurations (much like topic level) for brokers are managed
> by humans and automation systems through server.properties.
> Some configuration make sense to use default (like it is now) or override
> from central location (zookeeper for now). We can modify this through the new
> CLI tool so that every broker can have exact same setting. Some
> configurations we should allow to be overriden from server.properties (like
> port) but others we should use the global store as source of truth (e.g. auto
> topic enable, fetch replica message size, etc). Since most configuration I
> believe are going to fall into this category we should have the list of
> server.properties that can override the global config in the code in a list
> which we can manage... everything else the global takes precedence.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
