Hi Sam, If you see messageQueueSize is often close to limit and low CPU pressure on nodes, then limit value increasing can be helpful.
On Fri, Apr 21, 2017 at 11:36 PM, javastuff....@gmail.com < javastuff....@gmail.com> wrote: > Added below to TcpCommunicationSpi and message went away, able to see the > new > value on JMX as well. > /<property name="messageQueueLimit" value="1024"/>/ > > However, how do I know what is the good or suitable value one need to set? > I > have more than 50 different PARTITIONED OFF-HEAP caches defined, most > likely > to have 2 to 4 nodes with 20GB each or more. > > in my opinion, potential OOME is big risk with default configuration. > Everybody needs performance, but no one really need OOME. > > Thanks, > -Sam > > > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/stdout-Message-queue-limit-is-set-to- > 0-potential-OOMEs-tp12048p12165.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Best regards, Andrey V. Mashenkov
