> On April 18, 2014, 3:22 p.m., Jun Rao wrote:
> > core/src/main/scala/kafka/server/TopicConfigManager.scala, lines 123-124
> > <https://reviews.apache.org/r/20471/diff/1/?file=561891#file561891line123>
> >
> >     This is not needed. In ZK, new sequential nodes always get a higher id 
> > whether previous sequential nodes are deleted or not. ZK server maintains 
> > enough info to achieve that.
> 
> Jay Kreps wrote:
>     If you are totally sure I will remove that bit.

[zk: localhost:2181(CONNECTED) 2] create -s /a 1
Created /a0000000001
[zk: localhost:2181(CONNECTED) 3] delete /a0000000001
[zk: localhost:2181(CONNECTED) 4] create -s /a 2     
Created /a0000000003
[zk: localhost:2181(CONNECTED) 5] ls /a
[]
[zk: localhost:2181(CONNECTED) 6] ls / 
[a0000000003, zookeeper]


> On April 18, 2014, 3:22 p.m., Jun Rao wrote:
> > core/src/main/scala/kafka/server/TopicConfigManager.scala, lines 87-88
> > <https://reviews.apache.org/r/20471/diff/1/?file=561891#file561891line87>
> >
> >     The child list returned by ZK doesn't guarantee any ordering. We will 
> > need to sort this list so that we don't miss the latest config change.
> 
> Jay Kreps wrote:
>     I don't think this depends on any ordering.

Yes, you are right. It doesn't depend on ordering since it always reads from 
the config path in ZK.


- Jun


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/20471/#review40772
-----------------------------------------------------------


On April 18, 2014, 12:36 a.m., Jay Kreps wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/20471/
> -----------------------------------------------------------
> 
> (Updated April 18, 2014, 12:36 a.m.)
> 
> 
> Review request for kafka.
> 
> 
> Bugs: KAFKA-1398
>     https://issues.apache.org/jira/browse/KAFKA-1398
> 
> 
> Repository: kafka
> 
> 
> Description
> -------
> 
> KAFKA-1398 dynamic config changes are broken.
> 
> 
> Diffs
> -----
> 
>   core/src/main/scala/kafka/server/TopicConfigManager.scala 
> d41fd33d91406dfa2ce8c1e1b04a078e983ccadd 
>   core/src/test/scala/unit/kafka/server/DynamicConfigChangeTest.scala 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/20471/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Jay Kreps
> 
>

Reply via email to