[JBoss JIRA] Created: (ISPN-448) Consider all topology cache updates to be done by coordinator in Hot Rod
by Galder Zamarreno (JIRA)
Consider all topology cache updates to be done by coordinator in Hot Rod
------------------------------------------------------------------------
Key: ISPN-448
URL: https://jira.jboss.org/browse/ISPN-448
Project: Infinispan
Issue Type: Task
Components: Cache Server
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 5.0.0.BETA1
Based on the discussion below, consider all topology cache updates to be done by coordinator to avoid concurrency issues when updating it.
> Looks good.
> What is causing this unsuccessful add? If it is caused by timeouts due
> to multiple caches operating on the same key an alternative would be
> to only perform the operation on the coordinator and rest of the
> members to have node added listeners ...
Currently, each node when it starts, it's responsible of adding itself to the view and when it stops, it's responsible from removing itself. Apart from this, there's a crashed member listener running only in coordinator that detects whether any member left without updating the topology view. Your suggestion to have the coordinator control it all seems like could work and get around potential timeouts.
I'll create a JIRA to investigate this but won't do it for CR1 since I'm expect this to be a major issue. Metadata size is small and it's not constantly uddated.
--
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
12 years, 8 months
[JBoss JIRA] Created: (ISPN-1194) Consolidate rehash and replication state retrieval code
by Manik Surtani (JIRA)
Consolidate rehash and replication state retrieval code
-------------------------------------------------------
Key: ISPN-1194
URL: https://issues.jboss.org/browse/ISPN-1194
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache, State transfer
Affects Versions: 5.0.0.FINAL
Reporter: Manik Surtani
Assignee: Dan Berindei
Priority: Blocker
Fix For: 5.1.0.BETA1, 5.1.0.Final
As discussed. Abstract the actual code that handles moving of state so that it can be used both for rehashing as well as state transfer for replicated caches, thereby removing dependence on JGroups' FLUSH and partial state transfer.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (ISPN-1216) Separate delimiter processing lock timeouts in state transfer
by Galder Zamarreño (JIRA)
Separate delimiter processing lock timeouts in state transfer
-------------------------------------------------------------
Key: ISPN-1216
URL: https://issues.jboss.org/browse/ISPN-1216
Project: Infinispan
Issue Type: Enhancement
Components: State transfer
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.0.0.FINAL
It appears that majority of EOFException instances encountered during state transfer are due to lock acquisition problem in the processing lock.
So, consider adding a different limiter when the processing lock timeout is encountered. This should allow the receiving end to know more about the exact problem encountered by the sender side and so could provide more hints to the user.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (ISPN-302) Enable templated values for manually adding instances via jopr
by Galder Zamarreno (JIRA)
Enable templated values for manually adding instances via jopr
--------------------------------------------------------------
Key: ISPN-302
URL: https://jira.jboss.org/jira/browse/ISPN-302
Project: Infinispan
Issue Type: Feature Request
Components: JMX, reporting and management
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 4.1.0.BETA1
Enable templated values for manually adding instances via jopr
>> For manually importing - you should in the plugin descriptor put the JMX-remoting url as
>> >> default -- perhaps with the port as XXX, so the user does not have to copy& paste from an
>> >> external location, but only click in the text field and replace XXX by the real port.
>> >> same for Objectname of the cache manager.
> >
> > I did that. I told you it did not work and your reply was that it was fragile and you didn't looked into it further...
You / we were talking about c:template - which would allow to have several templates -- see jmx-plugin
e.g http://git.fedorahosted.org/git/rhq/rht.git?p=rhq/rhq.git;a=blob;f=module...
from line 47 on
What you can do, an which works is
<c:simple-property name="v1Community" type="string" default="public"/>
Here the default value 'public' is shown to the user for this property.
Sorry that I was confusing things
Heiko
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (ISPN-1358) expired entries must be removed with default configuration or <expiration> element
by Dmitry Shohov (JIRA)
expired entries must be removed with default configuration or <expiration> element
----------------------------------------------------------------------------------
Key: ISPN-1358
URL: https://issues.jboss.org/browse/ISPN-1358
Project: Infinispan
Issue Type: Enhancement
Components: Configuration
Affects Versions: 5.0.0.FINAL
Reporter: Dmitry Shohov
Assignee: Manik Surtani
EvictionManagerImpl which removes expired entries by calling purgeExpired() on dataContainer and cacheStore, does not start with default configuration. It requires <eviction> element which has mandatory maxEntries attribute and forces use of bounded cache.
Please make it start by default, or if it is not desirable in default configuration make it start with <expiration> element presented in configuration.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months