Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OOM command not allowed when used memory > maxmemory #433

Closed
GeoffreyPlitt opened this issue Jan 17, 2017 · 4 comments
Closed

OOM command not allowed when used memory > maxmemory #433

GeoffreyPlitt opened this issue Jan 17, 2017 · 4 comments

Comments

@GeoffreyPlitt
Copy link

I'm getting an error I don't quite understand. My guess is that I need to upgrade the memory for Redis. Is that right?

message: 'ERR Error running script (call to f_d5e879576feacc56627a3618fd6e20d53efe58de): @user_script:1: @user_script: 1: -OOM command not allowed when used memory > 'maxmemory'. ',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: command:
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: { name: 'evalsha',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: args:
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: [ 'd5e879576feacc56627a3618fd6e20d53efe58de',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: '6',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: 'bull:elasticsearch_indexer:wait',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: 'bull:elasticsearch_indexer:paused',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: 'bull:elasticsearch_indexer:meta-paused',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: 'bull:elasticsearch_indexer:jobs',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: 'bull:elasticsearch_indexer:id',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: 'bull:elasticsearch_indexer:delayed',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: 'bull:elasticsearch_indexer:',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: '',
Jan 17 10:15:43 stardust-backend app/changes_enqueuer.1: 'data',

@GeoffreyPlitt
Copy link
Author

Would cleaning queues resolve this?

@GeoffreyPlitt
Copy link
Author

Also wondering if tasks are automatically cleared on completion, or if a huge amount of completed tasks build up in redis

@bradvogel
Copy link
Contributor

You might be running into #426

@GeoffreyPlitt
Copy link
Author

Thanks! Looks like exactly the same, I'll subscribe to #426.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants