Issue 1:
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

I've seen that celery.backends.database.DatabaseBackend class has subpolling_interval as a private variable (with 0.5 value by default). It would be really helpful to move this variable to a configuration variable (maybe inside broker_transport_options dictionary or a new parameter called database_subpolling_interval) in order to modify this depends on every use case.

Design

Architectural Considerations

None

Proposed Behavior

None.

Proposed UI/UX

As I said above, this new configuration variable could be inside broker_transport_options with subpolling_interval as a name. Or also maybe create a new one called database_subpolling_interval.

Diagrams

N/A

Alternatives

None

Issue 2:
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

None

Possible Duplicates

None

Environment & Settings

Celery version:

celery report Output:

Steps to Reproduce

Required Dependencies

Minimal Python Version: 3.7.4

Minimal Celery Version: 4.3.0

Minimal Kombu Version: 4.6.3

Minimal Broker Version: RabbitMQ 3.8.3

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

Tried to configure connection friendly names in RabbitMQ for the connections made by Celery following the link : celery/kombu#1252

In celery config added the below configuration

broker_transport_options = {'client_properties': {

'connection_name': 'friendly-connection'}}

Expected that in the rabbitmq management console, this name would be available. But nothing happened. Not sure, if this is a bug or if there is something wrong in my configuration.

Actual Behavior