[
https://issues.jboss.org/browse/ISPN-3701?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-3701:
----------------------------------------
I'm not sure how much of an issue is this. The topology ID is indeed shared but
it's only updated upon a view change. Those events, compared to the number of times
that the topology id is read, which happens for each operation, are small. So, I'd say
that the topology ID is backed by a relatively low contention atomic integer, which should
not cause major issues.
Per-cache topology ID tracking could be implemented but I'm not sure there's much
benefit unless the server starts producing per-cache topology IDs, which it does not yet,
but it probably won't since we seem to be moving towards all caches being known to all
cache managers in a cluster.
In HotRod client topologyId is shared for all caches
----------------------------------------------------
Key: ISPN-3701
URL:
https://issues.jboss.org/browse/ISPN-3701
Project: Infinispan
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Remote Protocols
Affects Versions: 6.0.0.CR1
Reporter: Radim Vansa
Assignee: Galder Zamarreño
The AtomicInteger with topologyId is stored in RemoteCacheManager, therefore, shared for
all caches. This can lead to performance problems when accessing two caches with
non-synchronized topology ids.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)