Yes, each cluster message has a UUID, and at the receiver, duplicates are
eliminated.
Azeez
On Sat, Jul 6, 2013 at 5:25 PM, Sriskandarajah Suhothayan wrote:
>
> On Jul 4, 2013 6:39 PM, "Isuru Haththotuwa" wrote:
> >
> > Hi,
> >
> > On Thu, Jul 4, 2013 at 5:44 PM, Afkham Azeez wrote:
> >>
> >>
On Jul 4, 2013 6:39 PM, "Isuru Haththotuwa" wrote:
>
> Hi,
>
> On Thu, Jul 4, 2013 at 5:44 PM, Afkham Azeez wrote:
>>
>> There could be a situation where when a cluster message is sent, a
member momentarily leaves the cluster, but joins immediately. This
generally could happen when the nodes slow
Hi Azeez,
Totally +1 for the approach.
I can suggest some improvement if you haven't already done.
Several components in carbon platform will be using the hazelcast based
clustering impl. We should have some mechanism to embed the usage of the
each cluster message into the message itself.
For eg.
I have implemented a simple replay mechanism based on message UUIDs.
On Thu, Jul 4, 2013 at 5:44 PM, Afkham Azeez wrote:
> There could be a situation where when a cluster message is sent, a
> member momentarily leaves the cluster, but joins immediately. This
> generally could happen when the n
