When slave is attached and run stats tap in master, STAT eq_tapq has server information of master itself rather than slave machine (ZR #1)

reported by customer

(1) 1 master, 8 slaves
master and 7 slaves have build 1.5.3_r13
1 slave has build 1.5.2

(2)
Start slave with –e tap_peer=zstore-dev-mc3:11211
CLI looks like this:

LD_PRELOAD="/usr/local/gperftools/lib/libtcmalloc_minimal.so" /usr/local/bin/memcached d -p 11211 -u nobody -c 30000 -P /var/run/memcached/memcached.pid -E /usr/local/lib/ep.so -e "dbname=/ebs/zstore/test.db;tap_peer=zstore-dev<master_machine>:11211;ht_size=12582917;initfile=/tmp/init.sql" -r -v >/tmp/memcache.log 2>&1"

(3) attach slave

(4) run stats tap in master

ACTUAL RESULT:
STAT eq_tapq has server information of master itself rather than slave machine

I tried attaching a slave machine with build 1.5.2 and ran the stats tap again and I get the correct information (zstore-dev-mc13b). Below is stats tap I got from the master machine (zstore-dev-mc7)

zstore-dev-mc7
STAT tap_mutation_sent 17933
STAT tap_connect_received 6
STAT ep_tap_total_queue 0
STAT ep_tap_total_fetched 17920
STAT ep_tap_keepalive 0
STAT ep_tap_total_queue 0
STAT ep_tap_total_fetched 17920
STAT ep_tap_keepalive 0
STAT eq_tapq:zstore-dev-mc7:11211:qlen 0 <-- ISSUE
STAT eq_tapq:zstore-dev-mc7:11211:rec_fetched 8960 <-- ISSUE
STAT eq_tapq:zstore-dev-mc13b:11211:qlen 0 <-- running 1.5.2
STAT eq_tapq:zstore-dev-mc13b:11211:rec_fetched 8960 <-- running 1.5.2

machines:
zstore-dev-mc7 (as master)

All the below machines were attached as slaves to zstore-dev-mc7.
zstore-dev-mc7a
zstore-dev-mc7b
zstore-dev-mc6
zstore-dev-mc6a
zstore-dev-mc6b

one machine with older build (zmemcached-1.5.2-1.x86_64.rpm) installed was attached as slave to master (zstore-dev-mc7) for comparison purpose
zstore-dev-mc13b