RedisDataSet failed to retrieve dataset from AWS MemoryDB Redis instance

Joseph Roy <[email protected]> Tue, 6 Feb 2024 08:06:36 +0000
Newsgroups gmane.comp.jakarta.jmeter.user
Message-ID <SY8PR01MB8948A501869A4BCCD8F297D7C6462@SY8PR01MB8948.ausprd01.prod.outlook.com>
Hi all,



Has anyone tried running a test against Redis configured in AWS MemoryDB Redis instance? When I run a load/single-user test I get interim connection issues and it kills the thread.



In the logs, I see below:



2024-01-30 03:10:00,027 INFO o.a.j.r.Summariser: summary =  73168 in 00:03:32 =  345.3/s Avg:    16 Min:     0 Max:  1001 Err:     0 (0.00%)

2024-01-30 03:10:15,771 ERROR k.a.j.c.r.RedisDataSet: Failed to retrieve data from redis key summary_dataset

2024-01-30 03:10:15,774 INFO o.a.j.t.JMeterThread: Stop Thread seen for thread 5dJUWI0BGtJQzc6t0_V3 1-9, reason: org.apache.jorphan.util.JMeterStopThreadException: End of redis data detected

2024-01-30 03:10:15,776 INFO o.a.j.t.JMeterThread: Thread finished: 5dJUWI0BGtJQzc6t0_V3 1-9

2024-01-30 03:10:15,771 ERROR k.a.j.c.r.RedisDataSet: Failed to retrieve data from redis key summary_dataset

2024-01-30 03:10:15,779 INFO o.a.j.t.JMeterThread: Stop Thread seen for thread 5dJUWI0BGtJQzc6t0_V3 1-6, reason: org.apache.jorphan.util.JMeterStopThreadException: End of redis data detected

2024-01-30 03:10:15,779 INFO o.a.j.t.JMeterThread: Thread finished: 5dJUWI0BGtJQzc6t0_V3 1-6

2024-01-30 03:10:30,013 INFO o.a.j.r.Summariser: summary +  13893 in 00:00:30 =  463.3/s Avg:    16 Min:     0 Max:   530 Err:     0 (0.00%) Active: 10 Started: 12 Finished: 2

2024-01-30 03:10:30,027 INFO o.a.j.r.Summariser: summary =  87061 in 00:04:02 =  359.9/s Avg:    16 Min:     0 Max:  1001 Err:     0 (0.00%)

2024-01-30 03:11:00,023 INFO o.a.j.r.Summariser: summary +  13056 in 00:00:30 =  435.2/s Avg:    16 Min:     0 Max:    84 Err:     1 (0.01%) Active:

I have given the cluster URL for AWS MemoryDB Redis instance in the script. Redis cluster has implemented a slot migration not sure if it is coming into play here and how to handle that in the script, any thoughts?
Is there a way to give Redis startup_nodes in the script instead of cluster URLs to avoid AWS Redis Cluster - MOVE error?

Please suggest
Joe


Public