[SR-Users] Memory leak when reloading htable using db_cluster

Kristian F. Høgh kfh at uni-tel.dk
Fri Apr 28 08:17:33 CEST 2017


Hi list,

I use current git master.
When I reload a htable using "kamcmd htable.reload htable1", the "ctl handler" process leaks 384 bytes of pkg memory
If I use a direct mysql connection without db_cluster, the is no memory leak

modparam("db_cluster", "connection", "con1=>mysql://user:pass@ip.addr/database")
modparam("db_cluster", "connection", "con2=>mysql://user:pass@ip.addr2/database")
modparam("db_cluster", "cluster", "cls1=>con1=9s9s;con2=8s8s")

modparam("htable", "db_url", "cluster://cls1")
# modparam("htable", "db_url", "mysql://user:pass@ip.addr/database"
modparam("htable", "htable", "htable1=>size=8;autoexpire=0;dbtable=htable1;")

16(10429) ALERT: qm_status:    6513. N  address=0x7f4e65e01720 frag=0x7f4e65e016e8 size=128 used=1
16(10429) ALERT: qm_status:           alloc'd from db_cluster: dbcl_api.c: db_cluster_init(294)
16(10429) ALERT: qm_status:          start check=f0f0f0f0, end check= c0c0c0c0, abcdefed
16(10429) ALERT: qm_status:    6514. N  address=0x7f4e65e01808 frag=0x7f4e65e017d0 size=128 used=1
16(10429) ALERT: qm_status:           alloc'd from core: db.c: db_do_init2(298)
16(10429) ALERT: qm_status:          start check=f0f0f0f0, end check= c0c0c0c0, abcdefed
16(10429) ALERT: qm_status:    6515. N  address=0x7f4e65e018f0 frag=0x7f4e65e018b8 size=128 used=1
16(10429) ALERT: qm_status:           alloc'd from core: db.c: db_do_init2(298)
16(10429) ALERT: qm_status:          start check=f0f0f0f0, end check= c0c0c0c0, abcdefed

Regards,
Kristian Høgh
Uni-tel A/S

 



More information about the sr-users mailing list