Understanding pidbox queue names

[rgov]

I'm trying to debug a piece of third-party software that uses Celery (and therefore, indirectly, Kombu) for a remote control mailbox. I apologize for asking RTFM-able questions, but I spent a bit of time and could not unravel these.

It looks like somewhere in the stack a queue is created with a name like celery@hostname.reply.celery.pidbox. Note that this includes my computer's hostname, but some references I've found seem to use UUIDs instead of the hostname.

1. What is the celery@ part called / referring to? Actually what are all the parts of this referring to? It is kind of un-Googleable.
2. Is there a reason to override the celery@ (e.g., to associate it with the application user associated with the queue)? If so, how?
3. How do I override the use of the hostname?
4. In what cases is a UUID used instead of the hostname?
5. What is responsible for generating these names, Kombu or Celery? Does it vary based on the selected backend (e.g., RabbitMQ vs Redis)?

(Edit: I didn't see that discussions are enabled for this repo, feel free to transfer it there, or to the celery/celery repo if that's more appropriate.)

[open-collective-bot[bot]]

Hey @rgov 👋,
Thank you for opening an issue. We will get back to you as soon as we can.
Also, check out our Open Collective and consider backing us - every little helps!

We also offer priority support for our sponsors.
If you require immediate assistance please consider sponsoring us.