-
Notifications
You must be signed in to change notification settings - Fork 236
Description
In my test enviroment, I got the following outputs:
$ ./memtier_benchmark -s 192.168.111.126 -p 2001 -n 1 -c 1 -t 2 -d 20000 --cluster-mode
[RUN #1] Preparing benchmark client...
[RUN #1] Launching threads now...
[RUN #1 100%, 0 secs] 2 threads: 2 ops, 6557 (avg: 6557) ops/sec, 125.38MB/sec (avg: 125.38MB/sec), 0.39 (avg: 0.39) msec latency
It will hang here like forever. By reading the code, it seems it should exit and output like this:
[RUN #1] Preparing benchmark client...
[RUN #1] Launching threads now...
[RUN #1 100%, 0 secs] 0 threads: 2 ops, 0 (avg: 6756) ops/sec, 0.00KB/sec (avg: 129.20MB/sec), 0.00 (avg: 0.37) msec latency
2 Threads
1 Connections per thread
1 Requests per client
ALL STATS
Type Ops/sec Hits/sec Misses/sec MOVED/sec ASK/sec Latency KB/sec
Sets 6779.66 --- --- 0.00 0.00 0.37200 132746.29
Gets 0.00 0.00 0.00 0.00 0.00 0.00000 0.00
Waits 0.00 --- --- --- --- 0.00000 ---
Totals 6779.66 0.00 0.00 0.00 0.00 0.37200 132746.29
Request Latency Distribution
Type <= msec Percent
SET 0.350 50.00
SET 0.390 100.00
Why? My test environment is cluster mode.
Activity
vasiloeth commentedon Nov 28, 2019
Following up on this issue... any updates?
I'm facing the same problem
fix issue RedisLabs#94 cluster mode stuck
fix issue #94 cluster mode stuck (#106)
lc0305 commentedon Feb 13, 2021
Seems like the fix was removed from the mainline again. Any reason for this or was this by accident? #106
YaacovHazan commentedon Feb 14, 2021
Hi, @lc0305 the line was removed when we handled "fix issue #128 zeros in ouptut".
Do you still encounter the above "memtier_benchmark doest not exit as expected #94"?
lc0305 commentedon Feb 14, 2021
Yes it did not exit for me in cluster-mode when benchmarking against a remote host, but did exit when benchmarking against localhost.
I added the line from the previous fix and recompiled memtier and it fixed the issue for me.
YaacovHazan commentedon Feb 14, 2021
With the same command-line arguments? if not, can you share please the command line that you used?
lc0305 commentedon Feb 14, 2021
It did not exit with the default arguments except for
--cluster-mode -s -p
set to the remote IP address and port.benchmark ran on macOS 11
cluster ran on Debian 10 (Kernel 4.19)
YaacovHazan commentedon Feb 15, 2021
@lc0305 can you please, run it with
--debug
and share the output?Teddyhoang commentedon Jun 22, 2021
Get the same problem. Here the result with --debug

YaacovHazan commentedon Jun 22, 2021
@Teddyhoang not sure I got it... it seems that in your example the test exit as expected, no?
molian6 commentedon Jun 29, 2023
Hi there, I'm running into the same problem with it didn't exit running cluster mode. It stuck at 100%. Any idea on what causes it and potential fixes?
Thanks!
YaacovHazan commentedon Jun 29, 2023
@molian6, which version do you use? The new
2.0.0 version
includes a fix around cluster mode: #205molian6 commentedon Jun 29, 2023
I'm pulling the redislabs/memtier_benchmark:edge image, and looks like it's 2.0.0
YaacovHazan commentedon Jul 1, 2023
@molian6 can you run it with
--debug
and paste the output?17 remaining items