Glassfish 节点的最大数量？
我的公司已开始部署 Glassfish 作为我们选择的应用程序服务器。 （对于任何好奇的人，我们都喜欢它！）我们有多种产品，因此我们开始为每个产品设置一个集群。每个节点都是一个相当强大的盒子，因此每个节点在多个集群之间共享。
当我一直在努力扩大我们的部署时，我开始想知道 Glassfish 处理的节点数量是否有限制。我的理解是，一个给定的集群最多只能复制5个节点，但我还没有发现单个DAS（域管理服务器）管理的节点数量的限制。
有谁知道这样的限制是否存在？虽然如果我们可以通过一个用户界面管理数十个盒子中的数十个集群，那就太好了，但如果有必要的话，我宁愿现在就开始规划额外的 DAS 实例。
我检查了 Glassfish 文档，并向 Google 询问了六种不同的方式，所以我认为没有限制。但我想得到某种确认。
预先感谢大家！
（PS 每个人都应该尝试 Glassfish。如果你还在使用 Tomcat，你不知道你错过了什么！）
My company has begun deploying Glassfish as our app server of choice. (For anyone who's curious, we love it!) We have multiple products, so we've taken to setting up one cluster per product. Each node is a rather beefy box, so each node is shared across multiple clusters.
As I've been working to grow our deployments, I've begun wondering if there is a limit to the number of nodes that Glassfish will handle. My understanding is that a given cluster can only replicate up to 5 nodes, but I have not found a limit on the number of nodes managed by a single DAS (Domain Admin Server).
Does anyone know if such a limit exists? While it would be rather neat if we could manage dozens of clusters across dozens of boxes through a single user interface, I'd rather start planning for additional DAS instances now if they should become necessary.
I've checked the Glassfish docs and asked Google half-dozen different ways, so I think there's no limit. But I'd like to get some sort of confirmation on that.
Thanks in advance, everyone!
(P.S. Everyone should try Glassfish. If you're still using Tomcat, you don't know what you're missing!)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
首先，感谢您选择GlassFish！
以下是正式限制：
希望这有帮助！
约翰·克林根
GlassFish 服务器产品管理。
First of all, thank you for choosing GlassFish!
Here are the formal limits:
Hope this helps!
John Clingan
GlassFish Server Product Management.
在 Java One (2011) 的 Glassfish 会议上提出了这个确切的问题。我相信你可以在网上找到该视频。无论如何，当前的问题是管理控制台的限制，而不是容器本身的限制。随着节点帐户增长到大约 50 个，版本 2 似乎出现了问题。在版本 3 中，该限制据说要高得多。
ESPN 使用非常大的集群来运行“疯狂三月”。他们很久以前就遇到了极限，只是解决了这个问题，所以这不是一个阻碍。
ESPN 成功案例 - JavaOne 2011 上的 GlassFish 社区活动
At Java One (2011) this exact question was brought up in the Glassfish meetings. I'm sure you could find the video online. Anyway, the issue at hand was the limitation of the Admin Console rather than the container itself. Version 2 seemed to have issues as the node account grew to about 50. In version 3 the limit is supposedly much higher.
ESPN uses a very large cluster to run March Madness. They ran in to the limit a long time ago and just worked around it so it's not a show stopper.
ESPN Success Story - GlassFish Community Event at JavaOne 2011