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.

Sign up for GitHub

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

Jump to bottom

Switch from Redis to RabbitMQ as a message broker #42

Closed
ankitchiplunkar opened this issue Jul 5, 2018 · 0 comments
Closed

Switch from Redis to RabbitMQ as a message broker #42

ankitchiplunkar opened this issue Jul 5, 2018 · 0 comments
Milestone
0.1.0

Comments

@ankitchiplunkar
Copy link
Contributor

Describe the bug
Whie pushing blocks during the Shanghai attacks running multiple celery instances causes several issues.

  1. Same block numbers are being worked in parallelly by seperate workers
  2. Due to some blocks taking a few seconds and some blocks taking a few hours heartbeats are missed and Integrity errors are raised.

Expected behavior
Everything should run fine

Additional context
celery/celery#2296
This discussion says that the best resolution is to switch from Redis to RabbitMQ
@ankitchiplunkar ankitchiplunkar changed the title Switch from Redis stack to RabbitMQ Switch from Redis to RabbitMQ as a message broker Jul 5, 2018
@ankitchiplunkar ankitchiplunkar mentioned this issue Jul 6, 2018
Merged
7 tasks
@ankitchiplunkar ankitchiplunkar added this to the 0.1.0 milestone Jul 6, 2018
@ankitchiplunkar ankitchiplunkar mentioned this issue Jul 6, 2018
Merged
8 tasks
This was referenced Sep 9, 2019
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.1.0
Development

No branches or pull requests
1 participant
@ankitchiplunkar