Florian Jetter

> Why do we need it to begin with? That was my suggestion and is a prerequisite to allow breaking up decide_worker into multiple pieces. See also https://github.com/dask/distributed/issues/6922 for a...

> I agree we should aim to get this in main quickly and then further iterate. I can see two avenues: > > 1. get it in as-is (post minor...

I'm inclined to say this should be the responsibility of the deployment. On the generic level this library usually operates, I consider this low level configuration rather hard to maintain

I am open to this if it actually solves a problem. I am used to having a resource / cluster manager around killing misbehaving pods so I am a bit...

We should probably use this as an opportunity to enforce a couple of deprecations. For instance, the following arguments are no longer supported. it would be great if the new...

This is possibly closed by https://github.com/dask/distributed/pull/6847

If this causes problems, we can also revert https://github.com/dask/distributed/pull/6658 I still believe CWD is not a good choice for these things but it might be the lesser evil

Yes, I think the OP about permissions in a shared FS could be handled by better documentation. I think the shared system is a sufficiently rare case that we could...

> I don't think we should revert https://github.com/dask/distributed/pull/6658, due to the test suite. > If we do want to go back to CWD, we should > leave Nanny and Worker...

> > It is worth noting that most Linux filesystems provide /tmp via [tmpfs](https://en.wikipedia.org/wiki/Tmpfs), which effectively provides a RAM disk. > > Not quite - it's a ramdisk backed by...