[
https://issues.apache.org/jira/browse/KAFKA-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882439#comment-13882439
]
Jay Kreps commented on KAFKA-1229:
----------------------------------
The problem with doing this in general beyond the special case of per-topic
configurations is that many of the server variables can't currently be changed.
This happens for a number of reasons. Some settings are inherently unchangable,
i.e. socket buffer sizes may be are negotiated at connection time so can't
easily be changed. In other cases handling change is theoretically possible,
but very hard. For example the log cleaner uses a statically allocated buffer
so resizing it would introduce lots of complexity. In the rest of cases it is
not too hard but definitely adds a lot of complexity. Currently we use a
"dependency injection" style of programming where we pass in values via
constructors which are then used as immutable values. If these values can all
change at any time this becomes a lot harder. So although I think it would be
nice to have all config be dynamic I would vote against implementing it for now
as it would likely produce a lot of corner case bugs.
> Reload broker config without a restart
> --------------------------------------
>
> Key: KAFKA-1229
> URL: https://issues.apache.org/jira/browse/KAFKA-1229
> Project: Kafka
> Issue Type: Wish
> Components: config
> Affects Versions: 0.8.0
> Reporter: Carlo Cabanilla
> Priority: Minor
>
> In order to minimize client disruption, ideally you'd be able to reload
> broker config without having to restart the server. On *nix system the
> convention is to have the process reread its configuration if it receives a
> SIGHUP signal.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
