# Some plotters won't plot while CPU is idle

**URL:** <https://forum.autonomys.xyz/t/some-plotters-wont-plot-while-cpu-is-idle/4301>\
**Category:** Support\
**Created:** [June 26, 2024, 10:42pm UTC](https://forum.autonomys.xyz/t/some-plotters-wont-plot-while-cpu-is-idle/4301 "2024-06-26T22:42:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![keens312](https://avatars.discourse-cdn.com/v4/letter/k/90ced4/32.png) [@keens312](https://forum.autonomys.xyz/u/keens312)\
**Post date:** [June 26, 2024, 10:42pm UTC](https://forum.autonomys.xyz/t/some-plotters-wont-plot-while-cpu-is-idle/4301/1 "2024-06-26T22:42:45Z")

</div>

## Issue Report

Some plotters won’t plot with CPU usage 100% idle

### Environment

- **Operating System:** Ubuntu 18.04
- **Pulsar/Advanced CLI/Docker:** CLI

### Problem

Some plotters received plot request hang there for ever.  
It never completes and CPU usage is idle.  
What resource are they waiting for?

```auto
[Paste any errors or relevant logs here]

```

./subspace-farmer-jun-18 cluster --nats-server 192.168.0.39 plotter  
2024-06-26T22:05:09.579034Z INFO async\_nats: event:  
connected  
2024-06-26T22:05:10.472911Z INFO subspace\_farmer::commands::cluster::plotter: Preparing plotting thread pools plotting\_thread\_pool\_core\_indices=[CpuCoreSet {  
cores: CpuSet(0-7), .. }]  
2024-06-26T22:05:12.156425Z INFO {public\_key=d4a5986031ff8fdd76be484329d0d0ddca55921d78a2e6ffe1ec19fddc949670 sector\_index=16}: subspace\_farmer::cluster::plotter: Plot sector request  
2024-06-26T22:05:13.599907Z INFO {public\_key=d4a5986031ff8fdd76be484329d0d0ddca55921d78a2e6ffe1ec19fddc949670 sector\_index=12}: subspace\_farmer::cluster::plotter: Plot sector request

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [June 27, 2024, 1:49pm UTC](https://forum.autonomys.xyz/t/some-plotters-wont-plot-while-cpu-is-idle/4301/2 "2024-06-27T13:49:21Z")

</div>

There is no info about setup you have, but sounds like an issue fixed in [Skip duplicate node client notifications by nazar-pc · Pull Request #2882 · subspace/subspace · GitHub](https://github.com/subspace/subspace/pull/2882) that will be included in the next release