[KAFKA-1070] Auto-assign node id - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 0.9.0.0
Component/s: None
Labels:
- usability

Description

It would be nice to have Kafka brokers auto-assign node ids rather than having that be a configuration. Having a configuration is irritating because (1) you have to generate a custom config for each broker and (2) even though it is in configuration, changing the node id can cause all kinds of bad things to happen.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

KAFKA-1070_2015-01-12_18:30:17.patch
13/Jan/15 02:30
29 kB
Harsha
KAFKA-1070_2015-01-12_10:46:54.patch
12/Jan/15 18:47
28 kB
Harsha
KAFKA-1070_2015-01-01_17:39:30.patch
02/Jan/15 01:39
28 kB
Harsha
KAFKA-1070_2014-11-25_20:29:37.patch
26/Nov/14 04:29
43 kB
Harsha
KAFKA-1070_2014-11-20_10:50:04.patch
20/Nov/14 18:50
35 kB
Harsha
KAFKA-1070_2014-08-21_10:26:20.patch
21/Aug/14 17:26
47 kB
Harsha
KAFKA-1070_2014-07-24_21:05:33.patch
25/Jul/14 04:05
22 kB
Harsha
KAFKA-1070_2014-07-24_20:58:17.patch
25/Jul/14 03:58
33 kB
Harsha
KAFKA-1070_2014-07-22_11:34:18.patch
22/Jul/14 18:34
35 kB
Harsha
KAFKA-1070_2014-07-19_16:06:13.patch
19/Jul/14 23:06
18 kB
Harsha
KAFKA-1070.patch
19/Jul/14 00:24
205 kB
Harsha

Issue Links

is related to

KAFKA-3012 Avoid reserved.broker.max.id collisions on upgrade

Resolved

Activity

People

Assignee:: Harsha

Reporter:: Jay Kreps

Reviewer:: Neha Narkhede

Votes:: 3 Vote for this issue

Watchers:: 14 Start watching this issue

Dates

Created:: 02/Oct/13 15:59

Updated:: 18/Dec/15 16:59

Resolved:: 12/Jan/15 23:46