There does appear to be a recurring issue with the node logging closed connections from the other 2 nodes: https://gist.github.com/williamsjj/0481600566f10e5593c4
The other nodes though show no errors. -J On Mon, Jan 25, 2016 at 2:35 PM, Jason J. W. Williams < jasonjwwilli...@gmail.com> wrote: > > >> This is not an expected behavior. I think you may need to check >> replica fetcher threads to see why partitions are not getting replicated. >> > > I've been looking at the server.out logs, is there different place I > should be looking for the replica fetcher threads? > > >> Can you confirm that ISRon node never increased? >> > > Yeah I waited for a couple hours and no change. > > Thank you for your help so far. > > -J > > >> On Jan 24, 2016 12:33 PM, "Jason J. W. Williams" < >> jasonjwwilli...@gmail.com> >> wrote: >> >> > Hi Guys, >> > >> > I've set up a test cluster using 3 Vagrant nodes each running a Kafka >> > broker and zookeeper instance. Zookeepers are all linked properly and >> the >> > brokers appear to be registering properly. >> > >> > >> > After creating a new topic with 128 partitions and a replication factor >> of >> > 3 (https://gist.github.com/williamsjj/e52186da1ca708cf4f05), initially >> all >> > of the replicas show up under ISR...but within 30 seconds the 3rd node >> has >> > dropped from about 20% of the partitions: >> > >> > https://gist.github.com/williamsjj/7fdb931339263af5f401 >> > >> > Is that expected? >> > >> > -J >> > >> > >
