but they have always been up. I mean when i was testing, all the zookeepers were up. and all the kafka nodes were up. its just that I changed the number of zookeeper nodes in my first test iteration. second and third were still the same. not sure why the topics were losing some messages.
On Thu, Feb 19, 2015 at 11:39 AM, Jun Rao <j...@confluent.io> wrote: > Zookeeper requires a majority of the nodes to be up for the service to be > available. Kafka relies on Zookeeper to be always available. > > Thanks, > > Jun > > On Thu, Feb 19, 2015 at 11:15 AM, Karts <kartad...@gmail.com> wrote: > > > I have noticed some strange patterns when testing with the 0.8.1 build > and > > the 0.8.2 builds, and are listed below. > > 1. So I setup a brand new cluster [3 kafka nodes with 3 zookeepers], > > created 2 topics via the API calls, everything went fine and was > > successfully able to view my messages in my consumers. There were no > > messages lost. All is happy. Now, I change my setup to just have 1 > > zookeeper. and do my test again, i lose some messages. I have checked > that > > all my configs are pointing to just 1 zookeeper and there was no mention > of > > the other 2 offline zookeepers. any idea why ? > > 2. I revert back my settings to the original config, all 3 nodes are > > online, no errors, send messages to same old topic, and i am still > loosing > > some messages. I deleted all the old topic files [to follow the 'cleanup' > > process], create a new topic, and i am successfully able to receive all > > messages. no loss whatsoever. > > 3. Now in this state, i upgrade to 0.8.2, and try sending messages to the > > topic that was made after the above cleanup, and i am losing messages > > again. > > > > Am i making sense? I mean this is a very strange behavior, and if anyone > > can comment on this [please correct me if i have done something 'very' > > wrong].. > > > > Thanks.. > > >
