Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hey, I’m using a `LocalEnvironment` / `DaskCluster` to run my flow on a local cluster. Where does prefect report the LocalCluster provisioning logs? I’m interested in what port the UI is served (port 8787 is already taken on the server)

ping. does anyone know how to answer this? I actually also want to be able to connect to that scheduler from inside one of the tasks and I don’t know how

Hi Avi -  are you wanting to know the default base url for the UI when you're using Sever?  It's <http://localhost:8080>. If that wasn't what you were asking can you give me a bit more detail?  Thanks. 

no, I want to read the attributes of the dask scheduler that spawns when the job is running. I was expecting to find it in the prefect context when the flow is running, but it’s not there

the default scheduler address is `localhost:8786` but if for example if I’m running several flows on the same agent, with each of them spawning a local `DaskCluster`, I have no idea what is the scheduler for the flow I’m currently running in. I hope this makes it a bit clearer.

Ah - thanks for the clarification - that makes more sense.  Let me check with the team.

&gt; I actually also want to be able to connect to that scheduler from inside one of the tasks and I don’t know how

I don't recommend doing this based on the address of the dask cluster, but rather use a `worker_client` to get a client while inside a task running on a worker. Docs: <https://distributed.dask.org/en/latest/api.html#distributed.worker_client>

```from distributed import worker_client

@task
def example():
    with worker_client() as client:
        # do your dask stuff here```

<@U011EKN35PT> how do I make this client the default client? I’m not actually submitting a task on my own, I’m running a computation on a dask dataframe and would like the computation to be done on the existing cluster. I currently do this by:
```client = Client(existing_cluster_addr) # this implicitly makes the client the default execution entry for dask operations
...

dask_dataframe.operations.compute()```
so if I put Dask DataFrame operations inside the context in the code snippet you provided, will it run on the `client` from the context?

I don't recommend setting it as the default client, that will bleed outside of that single task and may affect other tasks. Rather, I recommend passing `scheduler=client` to `.compute` to specify which client to use.

sounds like a plan. I thought `scheduler` can only receive an address. Thanks a lot