question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

distributed.comm.tcp - WARNING - Closing dangling stream in <TCP> in compute() method

See original GitHub issue

Hi folks, I’m working with a 64GB dataset with 625882182 lines in a SLURM cluster (I’m using one machine with 128GB of RAM as 40 workers, also the interconnection between the workers and my workstations is Infiniband). So, I need to make the median and the quantile of one column, so I’m trying to gather this column to my workstation; however, this issue occurred during the perform : distributed.comm.tcp - WARNING - Closing dangling stream in <TCP>

These are my codes: njobs = df[df.phases != '-1'].njobs

njobs is:

npartitions=1043
   int64
     ...
   ...  
     ...
     ...
Name: njobs, dtype: int64
Dask Name: getitem, 5215 tasks

So when I ran: njobs = njobs.compute()

This warning occurred: distributed.comm.tcp - WARNING - Closing dangling stream in <TCP local=tcp://XXX.XXX.XXX:55166 remote=tcp://XXX.XXX.XXX:8786>

The data was gathered correctly, but I wonder to resolve this warning.

Thanks!

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:2
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
PabloPavancommented, Nov 29, 2019

@SultanOrazbayev I didn’t, sometimes this issue occurs, sometimes don’t. But for me, the results seem correct at all. I tested using the InfiniBand and the Ethernet, and it happened in both, so I think this issue is not the interconnection.

0reactions
mrocklincommented, Dec 7, 2019

Closing due to lack of information.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Closing dangling stream #2507 - dask/distributed - GitHub
This is indicated first by the dangling stream warning which is logged upon deletion of the TCP object and then the Setting TCP...
Read more >
Scheduler closing stream warning - python - Stack Overflow
I used with LocalCluster(**kwargs) as cluster: and a nested with Client(cluster) as client: to mitigate the dangling stream warning. I had ...
Read more >
Communications — Dask.distributed 2022.12.1 documentation
This will attempt to flush outgoing buffers before actually closing the underlying transport. This method returns a coroutine.
Read more >
Featuretools for Good | Kaggle
Create correlation matrix corr_matrix = data.corr() # Select upper triangle of ... distributed.comm.tcp - WARNING - Closing dangling stream in <TCP ...
Read more >
dask/dask - Gitter
buffer = BytesIO() ... CommClosedError: in <closed TCP>: Stream is closed. What's the correct way to start a cluster and let client compute...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found