[JBoss JIRA] Created: (ISPN-610) Apply isStateTransferEnabled attribute to consumer only
by craig bomba (JIRA)
Apply isStateTransferEnabled attribute to consumer only
-------------------------------------------------------
Key: ISPN-610
URL: https://jira.jboss.org/browse/ISPN-610
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Reporter: craig bomba
Assignee: craig bomba
Priority: Minor
Attachments: infinispan-core-state-trans.jar
We needed to be able to configure state transfer providers and consumers separately. The short term strategy is to make each node a provider. We then use the 'fetchInMemoryState' attribute to determine if a node can be a consumer or not.
org.infinispan.factories.StateTransferManagerFactory
Updated to remove the 'isStateTransferEnabled' check. Now every node is a state transfer provider.
org.infinispan.statetransfer.StateTransferManagerImpl
public void start()
Updated to now check the 'fetchInMemoryState' attribute to determine if this node can operate as a consumer.
public void generateState()
Updated so that any node can generate the state.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (ISPN-619) Aggregate changes from multiple transactions in AsyncStore
by Sanne Grinovero (JIRA)
Aggregate changes from multiple transactions in AsyncStore
----------------------------------------------------------
Key: ISPN-619
URL: https://jira.jboss.org/browse/ISPN-619
Project: Infinispan
Issue Type: Feature Request
Components: Loaders and Stores
Reporter: Sanne Grinovero
Assignee: Manik Surtani
Fix For: 5.0.0.BETA1
After debugging ISPN-618 we found out that the different changes of different transactions are not being coalesced in a smaller set of changes in the AsyncStore (see mailing list); we choose to solve ISPN-618 just fixing that bug, postponing the optimization idea as it would need more testing while ISPN-618 was found during CR3 testing.
The AsyncStore implementation should aggregate changes in a "transactions" variable in the same way as AbstractCacheStore, so to push only committed Modifications to the state-changes which are going to be async-applied to the delegated store.
So it seems to make sense to have AbstractDelegatingStore extend the AbstractCacheStore to inherit the same prepare/commit/rollback methods, but this affects all implementations of AbstractDelegatingStore.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (ISPN-611) Memcached issues with ruby client
by Tomaz Cerar (JIRA)
Memcached issues with ruby client
---------------------------------
Key: ISPN-611
URL: https://jira.jboss.org/browse/ISPN-611
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.1.0.CR3
Environment: Centos 5.5, Java 6u21, Ruby on Rails 2.3.2, Ruby Enterprise Edition 20090520
Reporter: Tomaz Cerar
Assignee: Manik Surtani
We have ROR application that uses MemCached for distributed cache.
As we have many issues with MemCached and its "clustering" we are considering to move to Infinispan for many goodies it provides.
The problem is that some commands that are issued against memcahe infinispan server die with error.
in ruby application we get errror:
ERROR -- : MemCacheError (unexpected response "VALUE views/semantic/1 0 674 \r\n"): unexpected response "VALUE views/semantic/1 0 674 \r\n"
and in infinispan log I can find:
2010-08-19 12:21:37,330 ERROR [org.infinispan.server.core.AbstractProtocolDecoder$] (MemcachedServerWorker-1-7) Exception reported
java.nio.channels.ClosedChannelException
I will try to provide sample code to demonstrate error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (ISPN-612) Allow substitution of Infinispan server properties
by Galder Zamarreno (JIRA)
Allow substitution of Infinispan server properties
--------------------------------------------------
Key: ISPN-612
URL: https://jira.jboss.org/browse/ISPN-612
Project: Infinispan
Issue Type: Feature Request
Components: Cache Server
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 4.1.0.Final
>From Brian S:
"Can whatever reads these properties (HotRodServer and MemcachedServer or some delegate) do system property substitution? Then the file has
infinispan.server.port = ${jboss.infinispan.server.port:11311}
or, if the substitution logic is simpler, even just
infinispan.server.port = ${jboss.infinispan.server.port}
and we tweak the config in datagrid/conf/bindingservice/beans to set jboss.infinispan.server.port"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months