[JBoss JIRA] Created: (ISPN-1348) Cluster ID generator initialization might not work when default cache is not clustered
3:55 a.m.
Cluster ID generator initialization might not work when default cache is not clustered
--------------------------------------------------------------------------------------
Key: ISPN-1348
URL: https://issues.jboss.org/browse/ISPN-1348
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.0.ALPHA1
This is related to the changes introduced as part of ISPN-1233. In Hot Rod servers,
cluster ID generator initialization can fail to assign an initial view rank if the default
cache is not clustered but other caches are. A better solution would be to simply cache
the cache manager on construction, and if a new version for a clustered cache is created
and the rank is not set yet (i.e. in cases such as AS7 where cache manager is started
before the servers themselves), use the cached cache manager's transport to quickly
calculate the view rank.
This won't happen with Memcached because you can only interact with the default
cache.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:20 a.m.
New subject: [JBoss JIRA] Work started: (ISPN-1348) Cluster ID generator initialization might not work when default cache is not clustered
[
https://issues.jboss.org/browse/ISPN-1348?page=com.atlassian.jira.plugin....
]
Work on ISPN-1348 started by Galder Zamarreño.
Cluster ID generator initialization might not work when default cache
is not clustered
--------------------------------------------------------------------------------------
Key: ISPN-1348
URL: https://issues.jboss.org/browse/ISPN-1348
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.0.ALPHA1
This is related to the changes introduced as part of ISPN-1233. In Hot Rod servers,
cluster ID generator initialization can fail to assign an initial view rank if the default
cache is not clustered but other caches are. A better solution would be to simply cache
the cache manager on construction, and if a new version for a clustered cache is created
and the rank is not set yet (i.e. in cases such as AS7 where cache manager is started
before the servers themselves), use the cached cache manager's transport to quickly
calculate the view rank.
This won't happen with Memcached because you can only interact with the default
cache.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:51 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-1348) Cluster ID generator initialization might not work when default cache is not clustered
[
https://issues.jboss.org/browse/ISPN-1348?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1348:
----------------------------------------
The reason for this JIRA is cos there's no easy way of retrieving the view ID from a
cache manager, see ISPN-1366.
Cluster ID generator initialization might not work when default cache
is not clustered
--------------------------------------------------------------------------------------
Key: ISPN-1348
URL: https://issues.jboss.org/browse/ISPN-1348
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.0.ALPHA1
This is related to the changes introduced as part of ISPN-1233. In Hot Rod servers,
cluster ID generator initialization can fail to assign an initial view rank if the default
cache is not clustered but other caches are. A better solution would be to simply cache
the cache manager on construction, and if a new version for a clustered cache is created
and the rank is not set yet (i.e. in cases such as AS7 where cache manager is started
before the servers themselves), use the cached cache manager's transport to quickly
calculate the view rank.
This won't happen with Memcached because you can only interact with the default
cache.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:07 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-1348) Cluster ID generator initialization might not work when default cache is not clustered
[
https://issues.jboss.org/browse/ISPN-1348?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1348:
----------------------------------------
The easiest way to solve this might be to turn ClusterIdGenerator into a global component
where we can inject the transport without any issues. That at the same time solves the
initialization timing issue.
Cluster ID generator initialization might not work when default cache
is not clustered
--------------------------------------------------------------------------------------
Key: ISPN-1348
URL: https://issues.jboss.org/browse/ISPN-1348
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.0.ALPHA1
This is related to the changes introduced as part of ISPN-1233. In Hot Rod servers,
cluster ID generator initialization can fail to assign an initial view rank if the default
cache is not clustered but other caches are. A better solution would be to simply cache
the cache manager on construction, and if a new version for a clustered cache is created
and the rank is not set yet (i.e. in cases such as AS7 where cache manager is started
before the servers themselves), use the cached cache manager's transport to quickly
calculate the view rank.
This won't happen with Memcached because you can only interact with the default
cache.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:35 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-1348) Cluster ID generator initialization might not work when default cache is not clustered
[
https://issues.jboss.org/browse/ISPN-1348?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1348:
----------------------------------------
Converting ClusterIdGenerator into a global component has the opposite side effect which
is, how do HR/Memcached servers get hold of it now when there's no access to global
component registry? This is slightly easier because we can get hold of the global
component registry via LifecycleCallbacks implementation and cache the ClusterIdGenerator
there.
Btw, converting ClusterIdGenerator has a slight impact which is that it's only in use
if tx recovery is enabled, or HR/Memcached servers are in use. At CacheManager startup
time, you know if tx recovery is on or not, but you don't know if HR/Memcached servers
will be in use. So, my current solution always creates a ClusterIdGenerator which is not
good.
It needs some further baking...
Cluster ID generator initialization might not work when default cache
is not clustered
--------------------------------------------------------------------------------------
Key: ISPN-1348
URL: https://issues.jboss.org/browse/ISPN-1348
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.0.ALPHA1
This is related to the changes introduced as part of ISPN-1233. In Hot Rod servers,
cluster ID generator initialization can fail to assign an initial view rank if the default
cache is not clustered but other caches are. A better solution would be to simply cache
the cache manager on construction, and if a new version for a clustered cache is created
and the rank is not set yet (i.e. in cases such as AS7 where cache manager is started
before the servers themselves), use the cached cache manager's transport to quickly
calculate the view rank.
This won't happen with Memcached because you can only interact with the default
cache.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:52 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-1348) Cluster ID generator initialization might not work when default cache is not clustered
[
https://issues.jboss.org/browse/ISPN-1348?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1348:
----------------------------------------
Actually, this is not a bug at all, or at least in the way the current code is written. As
per RpcManagerFactory, an RPCManager will be created per cache if the transport is not
null, regardless of the cache's mode. So, even if the cache mode is LOCAL, if the
cache manager has a transport set, getRpcManager won't return null and transport will
be retrievable.
So, this is not a bug at all. It's true though that RpcManagerFactory should not
create an RPCManager if the cache's mode is LOCAL, but that's a different issue
which I'll create in a minute. And before changing that, I need ISPN-1366 fixed in the
first place.
Cluster ID generator initialization might not work when default cache
is not clustered
--------------------------------------------------------------------------------------
Key: ISPN-1348
URL: https://issues.jboss.org/browse/ISPN-1348
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
This is related to the changes introduced as part of ISPN-1233. In Hot Rod servers,
cluster ID generator initialization can fail to assign an initial view rank if the default
cache is not clustered but other caches are. A better solution would be to simply cache
the cache manager on construction, and if a new version for a clustered cache is created
and the rank is not set yet (i.e. in cases such as AS7 where cache manager is started
before the servers themselves), use the cached cache manager's transport to quickly
calculate the view rank.
This won't happen with Memcached because you can only interact with the default
cache.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:52 a.m.
New subject: [JBoss JIRA] Resolved: (ISPN-1348) Cluster ID generator initialization might not work when default cache is not clustered
[
https://issues.jboss.org/browse/ISPN-1348?page=com.atlassian.jira.plugin....
]
Galder Zamarreño resolved ISPN-1348.
------------------------------------
Fix Version/s: (was: 5.1.0.ALPHA1)
Resolution: Rejected
Cluster ID generator initialization might not work when default cache
is not clustered
--------------------------------------------------------------------------------------
Key: ISPN-1348
URL: https://issues.jboss.org/browse/ISPN-1348
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
This is related to the changes introduced as part of ISPN-1233. In Hot Rod servers,
cluster ID generator initialization can fail to assign an initial view rank if the default
cache is not clustered but other caches are. A better solution would be to simply cache
the cache manager on construction, and if a new version for a clustered cache is created
and the rank is not set yet (i.e. in cases such as AS7 where cache manager is started
before the servers themselves), use the cached cache manager's transport to quickly
calculate the view rank.
This won't happen with Memcached because you can only interact with the default
cache.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4864
days inactive
4868
days old
infinispan-issues@lists.jboss.org
6 comments
1 participants
participants (1)
-
Galder Zamarreño (JIRA)