You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Apache Ignite as Cluster Manager, it is (as far as i could see in the code) not possible to overwrite the property messageQueueLimit as io.vertx.spi.cluster.ignite.IgniteOptions is missing the mapping for it.
Not defining the limit leads to a (valid) message on the console:
System.out:
org.apache.ignite.IgniteLogger - Message queue limit is set to 0 which may lead to potential OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to message queues growth on sender and receiver sides.
So it would be good to have the possibility to set the limit via the ignite.json file like:
Using Apache Ignite as Cluster Manager, it is (as far as i could see in the code) not possible to overwrite the property
messageQueueLimit
asio.vertx.spi.cluster.ignite.IgniteOptions
is missing the mapping for it.Not defining the limit leads to a (valid) message on the console:
So it would be good to have the possibility to set the limit via the ignite.json file like:
If this is found eligible, i volunteer implementing this.
Thanks and Best Regards!
The text was updated successfully, but these errors were encountered: