On Thu, Feb 26, 2015 at 4:08 PM, Aurélien Bras <aurelien.b...@gmail.com> wrote: > Hi, > > I have an issue configuring peer replication with stick tables. > > Here is my setup : > > peers mypeers > peer cldev-lb 10.1.1.101:1024 > > backend b_35902 > stick-table type ip size 1k store > bytes_out_rate(300000),bytes_in_rate(300000),bytes_out_cnt,bytes_in_cnt > peers mypeers > tcp-request content track-sc2 dst > > When reloading haproxy I can see, the learning process fetching data on port > 1024, and then the key still remain after, but all counter is reseted : > > Before the reload : > > echo "show table b_35902" | socat /var/run/haproxy/admin.sock stdio > # table: b_35902, type: ip, size:1024, used:1 > 0xd82e08: key=172.18.5.5 use=0 exp=0 bytes_in_cnt=3088 > bytes_in_rate(300000)=3088 bytes_out_cnt=14570 bytes_out_rate(300000)=14570 > > After : > > echo "show table b_35902" | socat /var/run/haproxy/admin.sock stdio > # table: b_35902, type: ip, size:1024, used:1 > 0x175ae08: key=172.18.5.5 use=0 exp=0 bytes_in_cnt=0 bytes_in_rate(300000)=0 > bytes_out_cnt=0 bytes_out_rate(300000)=0 > > Is it normal ? My goal is to keep theses counters across reload. > > Thanks for help. > > Regards. > > Aurélien
Hi Aurélien, Yes, this is normal and by design. Baptiste