动态配置分布式对象(Configuring Distributed Objects Dynamically)

 我目前正在评估使用Hazelcast作为我们的软件。 如果你能帮助我阐明以下内容，会很高兴。 
 
 我有一个特定的要求：我想能够动态地配置分布式对象（比如地图，队列等）。 也就是说，当我启动集群时，我无法掌握所有配置数据。 我希望能够根据需要初始化（和处理）服务，并且可以在它们之间改变它们的配置。 
 
 我正在评估的版本是3.6.2。 
 
 我可以获得的文档（参考手册，部署指南以及“Mastering Hazelcast”电子书）在这个主题上的细节很少，甚至是部分矛盾。 
 
 因此，澄清一个预期的用法：我想启动群集; 然后，在某个时候，创建一个分布式地图结构，在节点上使用它; 然后将其处置并使用具有不同配置的地图（例如，备份数量，驱逐策略）用于相同的目的。 
 
 文档提到，这是可以预料的，如果节点对同一个分布式对象有不同的配置，就会发生坏事。 这很合理，很好。 我可以确保配置一致。 
 
 看看代码，似乎可以做我想要的事情：在创建分布式对象时，如果它还没有代理，HazelcastInstance将查看其Config以创建一个新的并将其存储在其本地代理列表。 当该对象被销毁时，其代理将从列表中删除。 在下一次调用时，它会从Config中重新加载。 此外，该配置是可写的，所以如果它在两者之间被改变，它应该选择这些改变。 
 
 所以这看起来应该起作用，但鉴于文件对此事的沉默，我想要一些确认。 
 
 
 
 有没有任何理由为什么上述不应该工作？ 
 
 
 如果它应该起作用，是否有任何理由不这样做？ 例如，是否有计划在未来版本中更改代码，以防止这种情况发生？ 
 
 
 如果是这样，是否有其他选择？ 
 

I'm currently evaluating using Hazelcast for our software. Would be glad if you could help me elucidate the following.
 
I have one specific requirement: I want to be able to configure distributed objects (say maps, queues, etc.) dynamically. That is, I can't have all the configuration data at hand when I start the cluster. I want to be able to initialise (and dispose) services on-demand, and their configuration possibly to change in-between.
 
The version I'm evaluating is 3.6.2.
 
The documentation I have available (Reference Manual, Deployment Guide, as well as the "Mastering Hazelcast" e-book) are very skimpy on details w.r.t. this subject, and even partially contradicting.
 
So, to clarify an intended usage: I want to start the cluster; then, at some point, create, say, a distributed map structure, use it across the nodes; then dispose it and use a map with a different configuration (say, number of backups, eviction policy) for the same purposes.
 
The documentation mentions, and this is to be expected, that bad things will happen if nodes have different configurations for the same distributed object. That makes perfect sense and is fine; I can ensure that the configs will be consistent.
 
Looking at the code, it would seem to be possible to do what I intend: when creating a distributed object, if it doesn't already have a proxy, the HazelcastInstance will go look at its Config to create a new one and store it in its local list of proxies. When that object is destroyed, its proxy is removed from the list. On the next invocation, it would go reload from the Config. Furthermore, that config is writeable, so if it has been changed in-between, it should pick up those changes.
 
So this would seem like it should work, but given how silent the documentation is on the matter, I'd like some confirmation.
 
 
 
Is there any reason why the above shouldn't work?
 
 
If it should work, is there any reason not to do the above? For instance, are there plans to change the code in future releases in a way that would prevent this from working?
 
 
If so, is there any alternative?
 

原文：https://stackoverflow.com/questions/39876694