AbortError: Redis connection lost and command aborted. It might have been processed.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17.6k
- Forks
- 2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 40
Description
Here is my code
const rateLimit = require('express-rate-limit');
const redis = require('redis');
const RedisStore = require('rate-limit-redis');
let apiLimiter;
const client = redis.createClient(REDIS_CONFIG.PORT, REDIS_CONFIG.HOST);
client.on('error', err => console.info('ERR:REDIS:', err));
client.on('connect', () => console.info('INFO:REDIS:Connected!'));
apiLimiter = rateLimit({
store: new RedisStore({
client: client,
passIfNotConnected: true,
}),
windowMs: RATE_LIMIT.timerange,
max: RATE_LIMIT.count,
keyGenerator: 'mykeyhere',
message: { status: 'rateLimit', msg: RATE_LIMIT.message },
});
and this is the log

I got this error on my GCP(GAE and Redis) and don't know how to resolve it. Please help.
Environment
- Node.js Version:
12.x.x
- Redis Version:
5.o
- Platform:
macOS Big Sur 11.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied rate-limit-redis setup, Redis connection handlers, and the reported AbortError log, using the stated Node.js 12, Redis 5, macOS, and GCP environment details. A complete investigation would need to identify the cause and document a verified resolution, but the issue names no repository file, entry point, or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, redis
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100