[
https://issues.jboss.org/browse/ISPN-7682?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-7682:
------------------------------------
I agree, there's no "proper order" to update all these topology fields.
Initially I wanted to use a single field, but I think I hit some problems in the test
suite and went back to having a separate field in {{StateConsumerImpl}}. I'll see if I
can merge the {{TriangleOrderManager}} one, too.
DistributionManager's cache topology updated in wrong order
-----------------------------------------------------------
Key: ISPN-7682
URL:
https://issues.jboss.org/browse/ISPN-7682
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 9.0.0.CR3
Reporter: Radim Vansa
Assignee: Dan Berindei
{{StateTransferInterceptor}} sets command topology according to
{{StateTransferManager.getCacheTopology()}} which goes to {{StateConsumerImpl}}, but
{{EntryWrappingInterceptor}} routes according to
{{DistributionManager.getCacheTopology()}}. {{StateConsumer}}'s topology is set in
{{onTopologyUpdate}} before {{DistributionManager}}'s, and therefore a command can
have the current topology set, but EWI does not wrap the entry and some assertions in
{{BaseDistributionInterceptor.remoteGet}} fails.
This is a regression brought in ISPN-7400.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)