Open GoogleCodeExporter opened 8 years ago
# /usr/local/redis/redis-cli sync > r
# wc -l r
1493 r
# cat r | sed -e "s/\\x04.../\n/g" > r2
# wc -l r2
38396 r2
# /usr/local/redis/redis-cli dbsize
(integer) 38363
# wc -l red44.txt
40145 red44.txt
red44.txt is the file with hset data
Original comment by michaelp...@gmail.com
on 26 Apr 2011 at 2:32
Could you please check you do not have any key
duplicates in your red44.txt file?
Otherwise, 40 slaves directly connected to one master looks high to me.
Perhaps you should consider using some cascading (i.e. master connected
to 5 slaves, each of them connected to 8 other slaves ...).
Regards,
Didier.
Original comment by didier...@gmail.com
on 26 Apr 2011 at 3:37
(Thanks for your help)
Of course, red44.txt had not duplicate entry :)
i'm a little confuse, why an X number of slave machine can cause this problem ?
Original comment by michaelp...@gmail.com
on 26 Apr 2011 at 3:43
No duplicate entry
=> ok, we had to ask ;-)
Regarding the number of slave machines, it was an off topic remark.
I don't think there is a link between the number of items and
the number of slaves.
For your investigation, the next step is probably to use a keys *
command to dump all the keys and check their number.
1- if you have the expected number (i.e. same number than in red44.txt)
then there is definitely something strange in Redis.
2- if you have the same number than the result of dbsize and info,
then it means Redis is consistent, and some of your keys have not
been created while you think they have.
By comparing the result of keys * to your input file red44.txt,
(use shell commands to extract the keys), you can try to
identify the missing keys. Perhaps it will give you a new clue.
Regards,
Didier.
Original comment by didier...@gmail.com
on 26 Apr 2011 at 8:30
Original issue reported on code.google.com by
michaelp...@gmail.com
on 26 Apr 2011 at 2:20