Re: Observer doesn't write transactions?
Found the answer to my question. This has been fixed in 3.4.6 and 3.5.0 https://issues.apache.org/jira/browse/ZOOKEEPER-1552 On Mon, Jun 20, 2016 at 4:11 PM, Gokul wrote: > Hi Rakesh, > > I am testing locally. 2 servers(1 leader, 1 follower) and 1 observer > > *Server1* > > # The number of milliseconds of each tick > > tickTime=2000 > > # The number of ticks that the initial > > # synchronization phase can take > > initLimit=10 > > # The number of ticks that can pass between > > # sending a request and getting an acknowledgement > > syncLimit=5 > > # the directory where the snapshot is stored. > > dataDir=/tmp/zookeeper > > # the port at which the clients will connect > > clientPort=2181 > > server.1=0.0.0.0:2888:3888 > > server.2=0.0.0.0:4888:5888 > > server.3=0.0.0.0:6888:7888:observer > > *Server 2* > > # The number of milliseconds of each tick > > tickTime=2000 > > # The number of ticks that the initial > > # synchronization phase can take > > initLimit=10 > > # The number of ticks that can pass between > > # sending a request and getting an acknowledgement > > syncLimit=5 > > # the directory where the snapshot is stored. > > dataDir=/tmp/zookeeper2 > > # the port at which the clients will connect > > clientPort=3181 > > server.1=0.0.0.0:2888:3888 > > server.2=0.0.0.0:4888:5888 > > server.3=0.0.0.0:6888:7888:observer > *Server 3 ( Observer ) conf:* > > # The number of milliseconds of each tick > > tickTime=2000 > > # The number of ticks that the initial > > # synchronization phase can take > > initLimit=10 > > # The number of ticks that can pass between > > # sending a request and getting an acknowledgement > > syncLimit=5 > > # the directory where the snapshot is stored. > > dataDir=/tmp/zookeeper3 > > # the port at which the clients will connect > > clientPort=4181 > > server.1=0.0.0.0:2888:3888 > > server.2=0.0.0.0:4888:5888 > > server.3=0.0.0.0:6888:7888:observer > > peerType=observer > > On Mon, Jun 20, 2016 at 3:59 PM, Rakesh Radhakrishnan < > rakeshr.apa...@gmail.com> wrote: > >> Hey Gokul, >> >> Observer will write the transactions into the log file like other Follower >> servers. Could you share the server side configurations. Also, can you >> compare the Observer configurations with other Follower in your cluster to >> see any differences. >> >> Regards, >> Rakesh >> >> On Mon, Jun 20, 2016 at 3:43 PM, Gokul wrote: >> >> > Hi, >> > >> > I am using ZK version 3.4.5 >> > >> > I was running a 3 ZK servers locally with an Observer and observed that >> > Observer stores each transaction it gets from leader only in in-memory >> > snapshot and doesn't write the transaction to transaction log in disk. >> Is >> > this the expected behaviour or am I missing some config parameter? >> > >> > > > > -- > Thanks and Regards, > Gokul > -- Thanks and Regards, Gokul
Re: Observer doesn't write transactions?
Hi Rakesh, I am testing locally. 2 servers(1 leader, 1 follower) and 1 observer *Server1* # The number of milliseconds of each tick tickTime=2000 # The number of ticks that the initial # synchronization phase can take initLimit=10 # The number of ticks that can pass between # sending a request and getting an acknowledgement syncLimit=5 # the directory where the snapshot is stored. dataDir=/tmp/zookeeper # the port at which the clients will connect clientPort=2181 server.1=0.0.0.0:2888:3888 server.2=0.0.0.0:4888:5888 server.3=0.0.0.0:6888:7888:observer *Server 2* # The number of milliseconds of each tick tickTime=2000 # The number of ticks that the initial # synchronization phase can take initLimit=10 # The number of ticks that can pass between # sending a request and getting an acknowledgement syncLimit=5 # the directory where the snapshot is stored. dataDir=/tmp/zookeeper2 # the port at which the clients will connect clientPort=3181 server.1=0.0.0.0:2888:3888 server.2=0.0.0.0:4888:5888 server.3=0.0.0.0:6888:7888:observer *Server 3 ( Observer ) conf:* # The number of milliseconds of each tick tickTime=2000 # The number of ticks that the initial # synchronization phase can take initLimit=10 # The number of ticks that can pass between # sending a request and getting an acknowledgement syncLimit=5 # the directory where the snapshot is stored. dataDir=/tmp/zookeeper3 # the port at which the clients will connect clientPort=4181 server.1=0.0.0.0:2888:3888 server.2=0.0.0.0:4888:5888 server.3=0.0.0.0:6888:7888:observer peerType=observer On Mon, Jun 20, 2016 at 3:59 PM, Rakesh Radhakrishnan < rakeshr.apa...@gmail.com> wrote: > Hey Gokul, > > Observer will write the transactions into the log file like other Follower > servers. Could you share the server side configurations. Also, can you > compare the Observer configurations with other Follower in your cluster to > see any differences. > > Regards, > Rakesh > > On Mon, Jun 20, 2016 at 3:43 PM, Gokul wrote: > > > Hi, > > > > I am using ZK version 3.4.5 > > > > I was running a 3 ZK servers locally with an Observer and observed that > > Observer stores each transaction it gets from leader only in in-memory > > snapshot and doesn't write the transaction to transaction log in disk. Is > > this the expected behaviour or am I missing some config parameter? > > > -- Thanks and Regards, Gokul
Re: Observer doesn't write transactions?
Hey Gokul, Observer will write the transactions into the log file like other Follower servers. Could you share the server side configurations. Also, can you compare the Observer configurations with other Follower in your cluster to see any differences. Regards, Rakesh On Mon, Jun 20, 2016 at 3:43 PM, Gokul wrote: > Hi, > > I am using ZK version 3.4.5 > > I was running a 3 ZK servers locally with an Observer and observed that > Observer stores each transaction it gets from leader only in in-memory > snapshot and doesn't write the transaction to transaction log in disk. Is > this the expected behaviour or am I missing some config parameter? >
Observer doesn't write transactions?
Hi, I am using ZK version 3.4.5 I was running a 3 ZK servers locally with an Observer and observed that Observer stores each transaction it gets from leader only in in-memory snapshot and doesn't write the transaction to transaction log in disk. Is this the expected behaviour or am I missing some config parameter?
