Ok, well modifying the configuration might not be a good solution, what
if you have multiple nodes and the configurations files no longer match,
I guess you could create a service that runs on all nodes and have that
updating the XML configuration files when you add caches, there is no
need to "reload" the configuration while Ignite is running as you create
the caches manually from code AND update the XML configuration, and on a
restart the caches will be in the modified configuration.
Any chance you could enable persistence on the system cache ? that would
keep your created caches on restart.
The reason you cannot reload configuration while running is that many
settings cannot be changed on a running instance, page size, off heap
memory region sizes and so on.
Den 2020-06-30 kl. 11:15, skrev kay:
Hello :)
Because If I add cache by code, the cache disappears when the node is
restarted
so I want to modify the configuration file directly.
Thank you!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
