Even in version 1.104.1, the default value remains the same: 5. Release versions don’t have the fix yet.
I’m pretty sure you also have a CPU load problem (like in High CPU usage by nodes caused by receiving a new bloom filter while still processing the old one ) , just don’t expect that a single node would load all cores on your CPU. In this case, node would load one core to 100%. If you use Docker, please check the output of “sudo docker stats”, you’ll see CPU load caused by every node on the server.
And i believe that setting retain.concurrency to 1 should fix both problems: CPU load and processing new bloomfilter