failed to Put dial tcp 192.168.0.3:15127: connect: connection refused

[nabapadma]

I am getting a connection refusal error in redis server when the ops/sec is more than 2k or sometimes 3k .
I am using version v2(v2.0.5).
what would be the reason for this error.

[jongillham]

Are you able to replace the calls to this package with the default Google ones and see if it is the underlying service getting overloaded instead of anything to do with this package?

It could also bee that the API limits have changed (

nds/put.go

Line 16 in 8ce2dd5

const putMultiLimit = 500

) or there are more than an acceptable number of concurrent connections to the underlying infrastructure:

nds/put.go

Line 57 in 8ce2dd5

putKeys[i], errs[i] = c.putMulti(ctx, keys, vals.Interface())

[nabapadma]

@jongillham
but the problem is with the cache server. as far as the datastore don't have any issue with this putMultiLimit limit.
you see it is showing cache.DeleteMulti and cache.SetMulti connection refuse.
so are there any specific settings for redis server to avoid it or which end actually need to be debug to understand that?
did anyone face this connection refuse issues before.

[jongillham]

Apologies — I missed that it was the cache function. I wonder if @someone1 has any idea? I have not used the package in a long time.

I would potentially load test https://github.com/qedus/nds/blob/v2.0.5/cachers/redis/redis.go by itself if possible. I can't see anything to help when I search the web.

[nabapadma]

@jongillham
could you just make a load test script for https://github.com/qedus/nds/blob/v2.0.5/cachers/redis/redis.go .
that would be great.