Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apache Ignite Cluster Manager: Add possibility to customize messageQueueLimit via ignite.json #5228

Closed
scyv opened this issue Jun 6, 2024 · 1 comment

Comments

@scyv
Copy link

scyv commented Jun 6, 2024

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:

ignite.json:
{
  "messageQueueLimit": 1024,     <-- here
  "discoverySpi": {... },
  "cacheConfiguration": [...],
  "metricsLogFrequency": 0,
  "shutdownOnSegmentation": true
}

If this is found eligible, i volunteer implementing this.

Thanks and Best Regards!

@scyv
Copy link
Author

scyv commented Jun 7, 2024

sorry, i think this was the wrong repo. I reposted the issue here: vert-x3/vertx-ignite#140

@scyv scyv closed this as not planned Won't fix, can't repro, duplicate, stale Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant