[JBoss JIRA] (ISPN-2205) Design HotRod protocol version 1.2
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2205?page=com.atlassian.jira.plugin.... ]
Mircea Markus reopened ISPN-2205:
---------------------------------
> Design HotRod protocol version 1.2
> ----------------------------------
>
> Key: ISPN-2205
> URL: https://issues.jboss.org/browse/ISPN-2205
> Project: Infinispan
> Issue Type: Task
> Components: Remote protocols
> Affects Versions: 5.2.0.ALPHA2
> Reporter: Dan Berindei
> Assignee: Galder Zamarreño
> Labels: hotrod
>
> The consistent hash representation is changing in 5.2, and we need to modify the HotRod protocol to incorporate those changes. We preserved compatibility with 1.0/1.1 clients with a workaround on the server, but is not as efficient as it could be.
> The new version could also incorporate fixes for older issues like ISPN-1293.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (ISPN-3516) Remove deprecated API
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3516?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3516:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Remove deprecated API
> ---------------------
>
> Key: ISPN-3516
> URL: https://issues.jboss.org/browse/ISPN-3516
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 6.0.0.Alpha4
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Fix For: 6.0.0.Beta1
>
>
> classes:
> * org.infinispan.loaders.remote.wrapper.EntryWrapper
> * org.infinispan.context.FlagContainer
> methods:
> * StreamingMarshaller.startObjectOutput
> * AdvancedCache.getCacheEntry
> * AtomicMapLookup.getAtomicMap
> * DistributionManager.isLocal
> * TxInterceptor.setStatisticsEnabled
> * GridFile.delete
> * ModuleLifecycle.cacheManagerStarting
> * ModuleLifecycle.cacheStarting
> * DeadlockDetectingLockManager.getLocallyInterruptedTransactions
> packages:
> * org.infinispan.config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (ISPN-3520) Cassandra Cache Store is read-only by default
by Giovanni Mels (JIRA)
[ https://issues.jboss.org/browse/ISPN-3520?page=com.atlassian.jira.plugin.... ]
Giovanni Mels updated ISPN-3520:
--------------------------------
Attachment: PassivationTest.java
> Cassandra Cache Store is read-only by default
> ---------------------------------------------
>
> Key: ISPN-3520
> URL: https://issues.jboss.org/browse/ISPN-3520
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 5.2.6.Final, 6.0.0.Alpha4
> Reporter: Giovanni Mels
> Assignee: Mircea Markus
> Attachments: PassivationTest.java
>
>
> It is impossible to store any data in the Cassandra cache store, because it is created as read-only, even when specifying {{ignoreModifications = false}}. See the attached test case:
> [INFO ] ISPN000078: Starting JGroups Channel (org.infinispan.remoting.transport.jgroups.JGroupsTransport)
> [INFO ] ISPN000088: Unable to use any JGroups configuration mechanisms provided in properties {}. Using default JGroups configuration! (org.infinispan.remoting.transport.jgroups.JGroupsTransport)
> [INFO ] ISPN000094: Received new cluster view: [GNELA182-53637|0] [GNELA182-53637] (org.infinispan.remoting.transport.jgroups.JGroupsTransport)
> [INFO ] ISPN000079: Cache local address is GNELA182-53637, physical addresses are [fe80:0:0:0:64f5:4fad:cd2e:b5cf:51350] (org.infinispan.remoting.transport.jgroups.JGroupsTransport)
> [INFO ] ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.6.Final (org.infinispan.factories.GlobalComponentRegistry)
> [DEBUG] automatically create keyspace (org.infinispan.loaders.cassandra.CassandraCacheStore)
> [INFO ] ConnectionPool initialized. (net.dataforte.cassandra.pool.ConnectionPool)
> [DEBUG] cleaning up expired entries... (org.infinispan.loaders.cassandra.CassandraCacheStore)
> [TRACE] purgeInternal (org.infinispan.loaders.cassandra.CassandraCacheStore)
> [INFO ] ConnectionPool initialized. (net.dataforte.cassandra.pool.ConnectionPool)
> [DEBUG] started (org.infinispan.loaders.cassandra.CassandraCacheStore)
> *[TRACE] Ignoring clear invocation (org.infinispan.loaders.decorators.ReadOnlyStore)*
> [INFO ] ISPN000031: MBeans were successfully registered to the platform MBean server. (org.infinispan.jmx.CacheJmxRegistration)
> [INFO ] creating test1 (com.agfa.aca.PassivationTest)
> [DEBUG] Key 'entry_test1' not found (org.infinispan.loaders.cassandra.CassandraCacheStore)
> *[TRACE] Ignoring removal of key (org.infinispan.loaders.decorators.ReadOnlyStore)*
> [INFO ] created test1 (com.agfa.aca.PassivationTest)
> [INFO ] creating test2 (com.agfa.aca.PassivationTest)
> [DEBUG] Key 'entry_test2' not found (org.infinispan.loaders.cassandra.CassandraCacheStore)
> [INFO ] passivating test1 (com.agfa.aca.PassivationTest)
> *[TRACE] Ignoring store invocation (org.infinispan.loaders.decorators.ReadOnlyStore)*
> [INFO ] passivated test1 (com.agfa.aca.PassivationTest)
> *[TRACE] Ignoring removal of key (org.infinispan.loaders.decorators.ReadOnlyStore)*
> [INFO ] created test2 (com.agfa.aca.PassivationTest)
> [DEBUG] Key 'entry_test1' not found (org.infinispan.loaders.cassandra.CassandraCacheStore)
> I tracked this bug down to the {{create}} method in {{CassandraCacheStoreConfigurationBuilder}}
> {code}
> @Override
> public CassandraCacheStoreConfiguration create() {
> List<CassandraServerConfiguration> remoteServers = new ArrayList<CassandraServerConfiguration>();
> for (CassandraServerConfigurationBuilder server : servers) {
> remoteServers.add(server.create());
> }
> return new CassandraCacheStoreConfiguration(autoCreateKeyspace, configurationPropertiesFile, entryColumnFamily,
> expirationColumnFamily, framed, remoteServers, keyMapper, keySpace, password, sharedKeyspace, username,
> readConsistencyLevel, writeConsistencyLevel, autoCreateKeyspace, sharedKeyspace, purgerThreads, framed,
> autoCreateKeyspace, TypedProperties.toTypedProperties(properties), async.create(), singletonStore.create());
> }
> {code}
> Note how {{autoCreateKeyspace}} is used in stead of {{purgeInternal}} and {{ignoreModifications}}, so if you explicitly set {{autoCreateKeyspace = false}} you can work around the issue.
> This is tested on 5.2.6, all versions from 5.2 on have the same error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (ISPN-3520) Cassandra Cache Store is read-only by default
by Giovanni Mels (JIRA)
Giovanni Mels created ISPN-3520:
-----------------------------------
Summary: Cassandra Cache Store is read-only by default
Key: ISPN-3520
URL: https://issues.jboss.org/browse/ISPN-3520
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 6.0.0.Alpha4, 5.2.6.Final
Reporter: Giovanni Mels
Assignee: Mircea Markus
It is impossible to store any data in the Cassandra cache store, because it is created as read-only, even when specifying {{ignoreModifications = false}}. See the attached test case:
[INFO ] ISPN000078: Starting JGroups Channel (org.infinispan.remoting.transport.jgroups.JGroupsTransport)
[INFO ] ISPN000088: Unable to use any JGroups configuration mechanisms provided in properties {}. Using default JGroups configuration! (org.infinispan.remoting.transport.jgroups.JGroupsTransport)
[INFO ] ISPN000094: Received new cluster view: [GNELA182-53637|0] [GNELA182-53637] (org.infinispan.remoting.transport.jgroups.JGroupsTransport)
[INFO ] ISPN000079: Cache local address is GNELA182-53637, physical addresses are [fe80:0:0:0:64f5:4fad:cd2e:b5cf:51350] (org.infinispan.remoting.transport.jgroups.JGroupsTransport)
[INFO ] ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.6.Final (org.infinispan.factories.GlobalComponentRegistry)
[DEBUG] automatically create keyspace (org.infinispan.loaders.cassandra.CassandraCacheStore)
[INFO ] ConnectionPool initialized. (net.dataforte.cassandra.pool.ConnectionPool)
[DEBUG] cleaning up expired entries... (org.infinispan.loaders.cassandra.CassandraCacheStore)
[TRACE] purgeInternal (org.infinispan.loaders.cassandra.CassandraCacheStore)
[INFO ] ConnectionPool initialized. (net.dataforte.cassandra.pool.ConnectionPool)
[DEBUG] started (org.infinispan.loaders.cassandra.CassandraCacheStore)
*[TRACE] Ignoring clear invocation (org.infinispan.loaders.decorators.ReadOnlyStore)*
[INFO ] ISPN000031: MBeans were successfully registered to the platform MBean server. (org.infinispan.jmx.CacheJmxRegistration)
[INFO ] creating test1 (com.agfa.aca.PassivationTest)
[DEBUG] Key 'entry_test1' not found (org.infinispan.loaders.cassandra.CassandraCacheStore)
*[TRACE] Ignoring removal of key (org.infinispan.loaders.decorators.ReadOnlyStore)*
[INFO ] created test1 (com.agfa.aca.PassivationTest)
[INFO ] creating test2 (com.agfa.aca.PassivationTest)
[DEBUG] Key 'entry_test2' not found (org.infinispan.loaders.cassandra.CassandraCacheStore)
[INFO ] passivating test1 (com.agfa.aca.PassivationTest)
*[TRACE] Ignoring store invocation (org.infinispan.loaders.decorators.ReadOnlyStore)*
[INFO ] passivated test1 (com.agfa.aca.PassivationTest)
*[TRACE] Ignoring removal of key (org.infinispan.loaders.decorators.ReadOnlyStore)*
[INFO ] created test2 (com.agfa.aca.PassivationTest)
[DEBUG] Key 'entry_test1' not found (org.infinispan.loaders.cassandra.CassandraCacheStore)
I tracked this bug down to the {{create}} method in {{CassandraCacheStoreConfigurationBuilder}}
{code}
@Override
public CassandraCacheStoreConfiguration create() {
List<CassandraServerConfiguration> remoteServers = new ArrayList<CassandraServerConfiguration>();
for (CassandraServerConfigurationBuilder server : servers) {
remoteServers.add(server.create());
}
return new CassandraCacheStoreConfiguration(autoCreateKeyspace, configurationPropertiesFile, entryColumnFamily,
expirationColumnFamily, framed, remoteServers, keyMapper, keySpace, password, sharedKeyspace, username,
readConsistencyLevel, writeConsistencyLevel, autoCreateKeyspace, sharedKeyspace, purgerThreads, framed,
autoCreateKeyspace, TypedProperties.toTypedProperties(properties), async.create(), singletonStore.create());
}
{code}
Note how {{autoCreateKeyspace}} is used in stead of {{purgeInternal}} and {{ignoreModifications}}, so if you explicitly set {{autoCreateKeyspace = false}} you can work around the issue.
This is tested on 5.2.6, all versions from 5.2 on have the same error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (ISPN-3519) Upgrade to JGroups 3.4.0.Beta1
by Mircea Markus (JIRA)
Mircea Markus created ISPN-3519:
-----------------------------------
Summary: Upgrade to JGroups 3.4.0.Beta1
Key: ISPN-3519
URL: https://issues.jboss.org/browse/ISPN-3519
Project: Infinispan
Issue Type: Component Upgrade
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 6.0.0.Beta1
<email-from-bela>
I released 3.4.0.Beta1 yesterday. It contains delta views [1] and
compressed merge views [2]. Useful in large clusters, delta views
dramatically reduce the message size needed to install a new view, by
sending only the diff to the previous view. E.g. if we have
v5={A,B,C,D,E} and F joins, A will only send v6={v5 +F}, and everybody
will construct a new view v6={A,B,C,D,E,F}.
The message size of a new view is therefore only a function of the
number of members which joined or left, and not a function of the entire
cluster size.
Full views are only sent when the first view of a coordinator is sent,
e.g. if A crashes and B takes over, B would send the full view.
Delta views can be turned off by seting GMS.use_delta_views=false.
3.4.0.Beta1 can be downloaded from SourceForge [3] or Nexus [4].
3.4.0.Beta1 should be the last (and only) beta, I intend to release
3.4.0.Final in early October.
Cheers,
[1] https://issues.jboss.org/browse/JGRP-1354
[2] https://issues.jboss.org/browse/JGRP-1391
[3] https://sourceforge.net/projects/javagroups/files/JGroups/3.4.0.Beta1
[4]
http://search.maven.org/remotecontent?filepath=org/jgroups/jgroups/3.4.0....
</email-from-bela>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months