These are chat archives for nextflow-io/nextflow
.node-nextflow.logon the snubbed machine includes lines like:
May-10 16:51:07.332 [exchange-worker-#69%nextflow%] INFO o.a.i.i.p.c.GridCachePartitionExchangeManager - Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=2, minorTopVer=0], evt=NODE_JOINED, node=96c7d4b0-dc9b-4a9d-9a50-1b87bd4c512e
$ nextflow node -trace nextflow.daemon.CustomStealingCollisionSpi Unknown option: -trace -- Check the available commands and options and syntax with 'help'
nextflow -trace ... node
TRACE n.daemon.CustomStealingCollisionSpi - Node `localhost` resources > cpus: 12 (12) - mem: 15.6 GB (942.5 MB) - active: 0 - waiting: 34
# sync && echo 3 > /proc/sys/vm/drop_caches
0.19.0-SNAPSHOTwith a patch for #150, you may want to give it a try
It seems like TraceObserver already gets us most of the way there, no? The roadblock as I understand it is that DAG is only created after the pipeline runs.