-- Supun Malinga Sent from my phone. On 24 May 2013 02:37, "Afkham Azeez" <az...@wso2.com> wrote: > > There is no guarantee that the cluster message will be reliably delivered to all members. For instance, due to a momentary network delay or delay in the node, other members may detect that a member has left, but in reality, that member may be still running. If a cluster message, such as a DepSync message is sent in such a scenario, the node will not receive that message, and may never update its deployment repo.
Hi azeez, I understand the requirement and the need. But if the clustering has failed(member dropped) means that node will no longer receive load from the load balancer right? > > We could implement one of the following solutions; > 1. For selected cluster messages, we could replay them if a new member becomes available. We can't blindly replay all messages, but replaying the depsync message will cause no harm because the depsync operation is idempotent > > 2. For depsync, we can have periodic polling, but the polling interval should vary from about 1 minute to 5 minutes. > > -- > Afkham Azeez > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > > email: az...@wso2.com cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez > > Lean . Enterprise . Middleware > > _______________________________________________ > Dev mailing list > d...@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev >
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
