在 Grails 应用程序中添加/修改域类后重新启动 terracotta
我们有一个 Grails 应用程序,并且使用 Terracotta 进行缓存。我们注意到,每次我们在现有域类中添加一些字段或添加新的域类时,应用程序都会崩溃并显示“数据块意外结束...”,并且我们需要重新启动 terracotta 才能获得事情又开始运转了。
我们的架构是:
- 负载均衡器后面的两台服务器,各运行一个 grails 应用程序实例
- 单独的数据库服务器
- 在其中一台 Web 服务器上运行的 Terracotta
我们是否遗漏了一些东西?我们可以采取什么措施来避免每个域修改部署都出现这些停机时间?
更新:似乎是 Terracotta 问题:http:// forums.terracotta.org/forums/posts/list/5065.page
3.5 版本应该修复这个问题。让我们等待并希望吧!
谢谢,
伊拉克利斯
We have a Grails app, and we are using Terracotta for caching. We have noticed that every time we add some fields in existing domain classes or add new domain classes, the app crashes with "unexpected end of block of data..." and we need to restart terracotta to get things running again.
The architecture we have is:
- Two servers behind a load balancer, running a grails app instance each
- A separate DB server
- Terracotta running on one of the web servers
Are we missing something there? Is there anything we can do to avoid having these downtimes on every domain modifying deployment?
UPDATE: Seems like a Terracotta issue: http://forums.terracotta.org/forums/posts/list/5065.page
Version 3.5 should fix this issue. Let's just wait and hope!
Thanks,
Iraklis
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我们也使用 Terracotta 进行缓存,并且以前从未遇到过此错误。我们有一个与您类似的设置,负载均衡器后面有两个 Web 服务器,但区别在于 Terracotta 在一组不同的服务器中运行,我们有一个集群,其中一个服务器是主服务器,不确定这是否使虽然有区别,但至少是一个可以尝试的想法。
We use Terracotta for caching as well and never haven't gotten this error before. We have a similar set up as yours, two web servers behind a load balancer, but with the difference that Terracotta runs in a different set of servers, we have a cluster where one of the server is the master, not sure if this what makes the difference though but at least is an idea to try.