There are too many warning logs in the farmer cluster

[duanyz_aiyo]

@nazar-pc

So I see that above warning is the only one remaning. The only explanation I have right now is race condition in the way NATS handles multiple connections. Assuming that is in fact the case, this build should help: Snapshot build · subspace/subspace@7d0d9ac · GitHub
But I’m wondering if it will have any negative side-effects because of that.
Please give it a try and let me now if it is any better.

I have reported potential race condition upstream here: Race condition with multiple connections · Issue #1274 · nats-io/nats.rs · GitHub

We have tested for about 4 hours so far and haven’t found any warn logs yet

[nazar-pc]

Cool, I’ll include that in the next release then. Appreciate the feedback and testing!

[JeanS]

Hi, I do have same problem.
I am using Portainer Stack to define these;
Where this ‘–nats-pool-size 1’ should be added on my Stacks file? (I tried three places without success

Also should it be added to farm or plotter or both?

Here example piece of my Stacks file:
ss_farm1:
image: Package farmer · GitHub
volumes:
- /home/sub/nvme_drives/s980_1/data1:/subspace01
command:
[
“cluster”,
“–nats-server”, “nats:4222”,
“farmer”,
…

[nazar-pc]

There was a new release today that includes the change, just upgrade and there is nothing else that needs to be done: Release gemini-3h-2024-jun-11 · subspace/subspace · GitHub