Hello! You have to try different values of queue length, see what works best for you.
Ignite will not listen 2 different IPs. I'm pretty sure there are ways to turn 2 different physical interfaces into one logical one and bind on that. By setting local address you will specify which one you want to bind on. Regards, -- Ilya Kasnacheev чт, 6 дек. 2018 г. в 22:24, summasumma <bytestre...@gmail.com>: > Thanks for the details, Ilya. > > Even with connpair enabled, i got same issue when i pump in more data from > ycsb. > Then enabled MessageQueue=1024 as you have mentioned and now the issue is > gone. > > Not sure how to arrive at correct number for messagequeue though? can u pls > provide some inputs here since CPU also not utilized much.? > > One more clarification: > I see the network bandwidth is the limit getting hit in ignite. so wanted > to > scale horizontally and added one more interface with 1Gbps. But when i > added > following property under tcpcommunucationspi its throwing error and ignite > is not starting: > <property name="localAddress" value=<ip2>> > > Is it not possible to use Ignite node to start listening on 2 IP addresses > on 2 different interface in a VM? > Actually i have 3 interfaces in my VM, but the 1st interface is mgmt-port. > So wanted to bind on remaining 2 interfaces. Is it possible? > Note: I do not want to start another node with localaddress property set to > another IP since it will again occupy same amount of cache (in-memory) > which > will warrant to increase ram again. > > Please clarify. > > Thanks, > ...summa > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
