Distributed Queue status

Distributed
1

Hi Dask community!

Our team is considering implementing a distributed logging / record keeping functionality using the distributed.Queue class. However, despite being introduced in 2017 (as far as I can tell), it is still labeled as “experimental”. Aside from the usual precautions about how the API might change without warning, is there anything or any plans for this class we should be aware of? Is the experimental tag just a reflection that the object has not had much user testing and feedback up to now? Happy to get anyone’s thoughts or insights here.

2

Hi @elleryames,

I would say this is the main reason yes. But I’m ccing @fjetter or @crusaderky to confirm this.

3

Thanks for the reply @guillaumeeb !

4

It’s been around for a long time. I wouldn’t expect it to go anywhere. We should probably remove that warning.

2 Likes