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

None

Possible Duplicates

None

Environment & Settings

Celery version:

celery report Output:

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

Messages printed only one time from the worker.

Actual Behavior

2020-11-23 17:33:17:rasterprediction.predictor: DEBUG - _get_predict_package_path - Read config file: pesi/config_pesi.json

[2020-11-23 17:33:17,225: DEBUG/ForkPoolWorker-1] _get_predict_package_path - Read config file: pesi/config_pesi.json

2020-11-23 17:33:17:rasterprediction.predictor: DEBUG - Trying to retrieve predict package URI for task: TaskTypology.semantic_segmentation, and object: ObjectClass.building

[2020-11-23 17:33:17,226: DEBUG/ForkPoolWorker-1] Trying to retrieve predict package URI for task: TaskTypology.semantic_segmentation, and object: ObjectClass.building

2020-11-23 17:33:17:rasterprediction.predictor: DEBUG - Collected predict package URI: /var/www/django_projects/earthalytics-api/pesi/buildings_segmentation

[2020-11-23 17:33:17,226: DEBUG/ForkPoolWorker-1] Collected predict package URI: /var/www/django_projects/earthalytics-api/pesi/buildings_segmentation

Issue 2:
Checklist

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).

Related Issues and Possible Duplicates

Related Issues

None

Possible Duplicates

None

Description

The documentation https://docs.celeryproject.org/en/latest/history/whatsnew-4.0.html#latentcall-django-admonition is inconsistent when it comes to -*-_DB_SHORT_LIVED_SESSIONS.

I can't find guidance about what does -*- represents and what should be the final name on that setting.

I have tried CELERY_DEFAULT_DB_SHORT_LIVED_SESSIONS but the 2006 MySQL problem is supposed to fix continues to happen so I assume the setting is wrong. We need a clearer doc on how to use that setting.

Suggestions

Give an example on how the configuration should look in a Django file and explain what -*- represents. Also, I have seen it as [...] in other places so it should be consistent unless it's meant to be intentionally different.