tag:blogger.com,1999:blog-59077094557892.post2193993033124861825..comments2023-07-23T01:55:47.278-07:00Comments on Evanthika Amarasiri's Blog: Expiration times of L1 & L2 caches with Hazelcast for WSO2 productsEvanthikahttp://www.blogger.com/profile/02913709559298376105noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-59077094557892.post-10786027280966408552014-07-31T09:35:06.736-07:002014-07-31T09:35:06.736-07:00Hi,
Yes. This is a known issue. As a workaround, ...Hi,<br /><br />Yes. This is a known issue. As a workaround, you can have multiple wka nodes in your cluster. For example, if you have a management node and worker nodes, you can make these wka nodes. So if you restart the ELB node, you need not to restart the entire cluster. The other wka nodes will take care of the cluster.<br /><br />Regards,<br />EvanthikaEvanthikahttps://www.blogger.com/profile/02913709559298376105noreply@blogger.comtag:blogger.com,1999:blog-59077094557892.post-6070672865440734472014-07-30T01:17:15.517-07:002014-07-30T01:17:15.517-07:00Hi Evanthika,
I tried a cluster of wso2 services w...Hi Evanthika,<br />I tried a cluster of wso2 services with management and worker nodes fronted by an elb node (the cluster coordinator). The cluster is using the hazelcast protocol. All works fine but if I restart the elb the other nodes dont reconnect to the elb node, so i must restart all other nodes too.<br />Is there a way to overcome this problem?<br />TK in advancegraziano1955https://www.blogger.com/profile/10528946143180221978noreply@blogger.com