Issue 1:
Checklist

I have verified that the issue exists against the master branch of Celery.

This has already been asked to the discussion group first.

I have read the relevant section in the

contribution guide

on reporting bugs.

I have checked the issues list

for similar or identical bug reports.

I have checked the pull requests list

for existing proposed fixes.

I have checked the commit log

to find out if the bug was already fixed in the master branch.

I have included all related issues and possible duplicate issues

in this issue (If there are none, check this box anyway).

Mandatory Debugging Information

I have included the output of celery -A proj report in the issue.

(if you are not able to do this, then at least specify the Celery

version affected).

I have verified that the issue exists against the master branch of Celery.

I have included the contents of pip freeze in the issue.

I have included all the versions of all the external dependencies required

to reproduce this bug.

Optional Debugging Information

I have tried reproducing the issue on more than one Python version

and/or implementation.

I have tried reproducing the issue on more than one message broker and/or

result backend.

I have tried reproducing the issue on more than one version of the message

broker and/or result backend.

I have tried reproducing the issue on more than one operating system.

I have tried reproducing the issue on more than one workers pool.

I have tried reproducing the issue with autoscaling, retries,

ETA/Countdown & rate limits disabled.

I have tried reproducing the issue after downgrading

and/or upgrading Celery and its dependencies.

Related Issues and Possible Duplicates

Related Issues

Has recently been used celery for multi-process concurrent tasks, met a very difficult problem, I tried to solve, but to collect a variety of methods, failed to solve my problem.

Problem: Celery multitasking program, the task using inherited classes encapsulate Celery. Task type of task to complete my task, task, of course, include my success and failure of rewriting method.My program is not important, of course, just a program will appear, kombu. Exceptions. OperationalError mistake, Cannot route message for exchange 'reply.celery.pidbox': Table emply or key no longer exists, I'll find related to explain the key as redis reply. Celery. Pidbox ousted, lead to the routing problem, which I doubt is redis configuration problem, I tried to existing have been fighting for using redis cluster, will quote us pidbox ousted, same problem.Then I was celery there may be some problems, please the great god still hope to give directions, thank you very much

Possible Duplicates

None

Environment & Settings

Celery version:

python 3.6.5

celery 4.3.0

redis 3.2.1 （Using the cluster）

kombu 4.6.2 (4.6.4 4.6.5 Try to release)

celery report Output:

kombu.exceptions.OperationalError：
Cannot route message for exchange 'reply.celery.pidbox': Table emply or key no longer exists

RuntimeError: pubsub connection not set: did you forget to call subscribe() or psubscribe()?

Steps to Reproduce

Required Dependencies

Minimal Python Version: N/A or Unknown

Minimal Celery Version: N/A or Unknown

Minimal Kombu Version: N/A or Unknown

Minimal Broker Version: N/A or Unknown

Minimal Result Backend Version: N/A or Unknown

Minimal OS and/or Kernel Version: N/A or Unknown

Minimal Broker Client Version: N/A or Unknown

Minimal Result Backend Client Version: N/A or Unknown

Python Packages

pip freeze Output:

Other Dependencies

N/A

Minimally Reproducible Test Case

Expected Behavior

Actual Behavior

Issue 2:
Checklist

I have checked the issues list

for similar or identical feature requests.

I have checked the pull requests list

for existing proposed implementations of this feature.

I have checked the commit log

to find out if the if the same feature was already implemented in the

master branch.

I have included all related issues and possible duplicate issues

in this issue (If there are none, check this box anyway).

Related Issues and Possible Duplicates

Related Issues

None

Possible Duplicates

None

Brief Summary

Design

Architectural Considerations

None

Proposed Behavior

Proposed UI/UX

Diagrams

N/A

Alternatives

None