Ok here is what I have done. All instance of handling ViewChangeEvent now handle
MergeEvent as well. I believe this is how it used to be before the ViewChangeEvent and
MergeEvent split in 4.2. I made MergeEvent extend ViewChangeEvent, therefore all we had to
do is to attach @Merged to already existing listeners. I have verified handling of merge
for DistributionManager. I also enabled rehashing test under merge scenario. It now
passes. There were no other regressions on test suite.
Will you (if you are familiar) have a look at SingletoStore, KeyAffinityService and
TransactionTable?
The relevant change set is
Talk to you guys Tuesday (Long weekend in Canada:)),
Vladimir
On 2010-10-08, at 10:23 AM, Vladimir Blagojevic wrote:
Wherever we used to listen for ViewChangeEvents we now have to listen
for MergeEvents as well, don't we? I've looked around and I believe that there are
four internal areas of our codebase that need to adapt to these changes:
KeyAffinityService, DistributionManager, SingletonStore and TransactionTable. I'll
handle DsitributionManager, and the others, if you are familiar with the codebase please
have a look and talk to me privately so we can coordinate further.
Regards,
Vladimir
On 2010-10-07, at 10:47 AM, Vladimir Blagojevic wrote:
> Good point. It is related to
https://jira.jboss.org/browse/ISPN-609
> Seem like Manik wanted to introduce separate event for merge scenarios. But why did
he not finish full implementation of it? Maybe an oversight. I am tempted to complete it
because we can not push 4.2 without this finished...
>
>
>
>
> On 2010-10-07, at 9:10 AM, Galder ZamarreƱo wrote:
>
>> At first glance, no idea. Did you check the commit that introduce these classes
to see if you could some clues through that?
>>
>> On Oct 6, 2010, at 8:00 PM, Vladimir Blagojevic wrote:
>>
>>> Hey,
>>>
>>> I wanted to re-enable and implement some additional partition merge tests
when I noticed, what seems, some unfinished work in merge event notification. I see that
Manik added Merged annotation and MergeEvent in 4.2 which are similar to ViewChanged
annotation and ViewChangedEvent except that they are exclusively used for merge view
notifications. Anyway, JGroups MergeView is detected in JGroupsTransport, listeners are
invoked except that Merge notification is not allowed to propagate in
CacheManagerNotifierImpl! In addition to this DistributionManagerImpl does not register
listener for Merge event notification!
>>>
>>> Does anyone know what is going on here? Why is this mechanism left
unfinished?
>>>
>>>
>>> Regards,
>>> Vladimir
>>>
>>> --
>>> Vladimir Blagojevic
>>> JBoss Clustering Team
>>> JBoss, by Red Hat
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>> --
>> Galder ZamarreƱo
>> Sr. Software Engineer
>> Infinispan, JBoss Cache
>>
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> --
> Vladimir Blagojevic
> JBoss Clustering Team
> JBoss, by Red Hat
>
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Vladimir Blagojevic
JBoss Clustering Team
JBoss, by Red Hat
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev