January 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-858) Calculated ETag not accurate enough

by Galder Zamarreño (JIRA)

Calculated ETag not accurate enough ----------------------------------- Key: ISPN-858 URL: https://issues.jboss.org/browse/ISPN-858 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 5.0.0.ALPHA1, 4.2.0.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.1.Final, 5.0.0.BETA1 MIMECacheEntry's lastModified attribute only has second accuracy, so you updates that are performed in same second where content type and length stays the same, a collision occurs - ETag stays the same although the values are not identical. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
9
0 / 0

[JBoss JIRA] Updated: (ISPN-186) Smart L1 cache invalidation

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-186?page=com.atlassian.jira.plugin.s... ] Manik Surtani updated ISPN-186: ------------------------------- Comment: was deleted (was: This blog post speaks briefly about colocation, and how this can be achieved using AtomicMaps. http://infinispan.blogspot.com/2009/08/distribution-instead-of-buddy.html) > Smart L1 cache invalidation > --------------------------- > > Key: ISPN-186 > URL: https://issues.jboss.org/browse/ISPN-186 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Manik Surtani > Assignee: Pete Muir > Labels: colocation > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > Need to build a mechanism in which L1 invalidation is NOT multicast, but instead is unicast _if necessary_ to specific nodes that may have cached a given entry. This can be detected by maintaining a list of nodes who have requested a key via a remote get, but this would need to be relayed by all data owners. > Benefits would be performance by removing unnecessary invalidation where this is not needed, and by reducing noise in network stacks of most nodes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (ISPN-186) Smart L1 cache invalidation

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-186?page=com.atlassian.jira.plugin.s... ] Manik Surtani commented on ISPN-186: ------------------------------------ This blog post speaks briefly about colocation, and how this can be achieved using AtomicMaps. http://infinispan.blogspot.com/2009/08/distribution-instead-of-buddy.html > Smart L1 cache invalidation > --------------------------- > > Key: ISPN-186 > URL: https://issues.jboss.org/browse/ISPN-186 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Manik Surtani > Assignee: Trustin Lee > Labels: hackathon > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > Need to build a mechanism in which L1 invalidation is NOT multicast, but instead is unicast _if necessary_ to specific nodes that may have cached a given entry. This can be detected by maintaining a list of nodes who have requested a key via a remote get, but this would need to be relayed by all data owners. > Benefits would be performance by removing unnecessary invalidation where this is not needed, and by reducing noise in network stacks of most nodes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (ISPN-186) Smart L1 cache invalidation

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-186?page=com.atlassian.jira.plugin.s... ] Manik Surtani reassigned ISPN-186: ---------------------------------- Assignee: Pete Muir (was: Trustin Lee) > Smart L1 cache invalidation > --------------------------- > > Key: ISPN-186 > URL: https://issues.jboss.org/browse/ISPN-186 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Manik Surtani > Assignee: Pete Muir > Labels: hackathon > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > Need to build a mechanism in which L1 invalidation is NOT multicast, but instead is unicast _if necessary_ to specific nodes that may have cached a given entry. This can be detected by maintaining a list of nodes who have requested a key via a remote get, but this would need to be relayed by all data owners. > Benefits would be performance by removing unnecessary invalidation where this is not needed, and by reducing noise in network stacks of most nodes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-855) Review logger usage in query module

by Sanne Grinovero (JIRA)

Review logger usage in query module ----------------------------------- Key: ISPN-855 URL: https://issues.jboss.org/browse/ISPN-855 Project: Infinispan Issue Type: Task Components: Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Optional there are some non-static loggers, some unneeded checks for logging level, and most importantly some uninitialized loggers (which are then used, no clue how it didn't throw NPEs: likely classes where never invoked/ covered in tests) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-852) Reduce TransactionLoggerImpl logging

by Galder Zamarreño (JIRA)

Reduce TransactionLoggerImpl logging ------------------------------------ Key: ISPN-852 URL: https://issues.jboss.org/browse/ISPN-852 Project: Infinispan Issue Type: Task Affects Versions: 5.0.0.ALPHA1, 4.2.0.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1 Too many of these: 03:39:06,603 INFO [TransactionLoggerImpl] Starting transaction logging 03:39:06,623 INFO [TransactionLoggerImpl] Stopping transaction logging Should be switched to debug. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
10
0 / 0

[JBoss JIRA] Created: (ISPN-853) MBean registration happening twice

by Galder Zamarreño (JIRA)

MBean registration happening twice ---------------------------------- Key: ISPN-853 URL: https://issues.jboss.org/browse/ISPN-853 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 5.0.0.ALPHA1, 4.2.0.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1 Is MBean registration happening twice for same MBean? Investigate this: "MBean registration tries twice the same MBean, the second time fails and prints log (no harm besides that, the process continues without failures): 03:39:06,395 INFO [ComponentsJmxRegistration] Could not register object with name: org.infinispan:type=Cache,name="___defaultcache(dist_sync)",manager="DefaultCacheManager",component=Cache" -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (ISPN-846) In HotRod, errors reading the header should not be hidden

by Galder Zamarreño (JIRA)

In HotRod, errors reading the header should not be hidden --------------------------------------------------------- Key: ISPN-846 URL: https://issues.jboss.org/browse/ISPN-846 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 5.0.0.ALPHA1, 4.2.0.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1, 5.0.0.Final If Hot Rod has an issue reading the header (for example, the cache name), the actual issue gets hidden in the logs: 2010-12-21 10:02:49,948 TRACE [HotRodEncoder$] (HotRodServerWorker-1-1) Encode msg GetResponse{messageId=1, operation=GetResponse, status=KeyDoesNotExist, data=null} 2010-12-21 10:02:50,100 TRACE [Decoder10$] (HotRodServerWorker-1-2) Operation code: 3 has been matched to GetRequest 2010-12-21 10:02:50,538 ERROR [AbstractProtocolDecoder$] (HotRodServerWorker-1-2) Exception reported java.util.NoSuchElementException: None.get at scala.None$.get(Option.scala:262) at scala.None$.get(Option.scala:260) at org.infinispan.server.hotrod.HotRodDecoder.createServerException(HotRodDecoder.scala:138) at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:55) Add better error handling for such situations. This came from trying to debug the Python Hot Rod client. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (ISPN-844) Better documentation for infinispan.module.name

by Galder Zamarreño (JIRA)

Better documentation for infinispan.module.name ----------------------------------------------- Key: ISPN-844 URL: https://issues.jboss.org/browse/ISPN-844 Project: Infinispan Issue Type: Task Components: Configuration Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1 In the Infinispan Module Lifecycle configuration, "infinispan.module.name" needs to be better documented. All it's used is to differentiate between diff modules, since it becomes the key of an internal map. So, you can actually use anything for this property, but you don't want two diff modules using the same string. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-843) Externalizer config not correctly returned when using addExternalizer() API

by Galder Zamarreño (JIRA)

Externalizer config not correctly returned when using addExternalizer() API --------------------------------------------------------------------------- Key: ISPN-843 URL: https://issues.jboss.org/browse/ISPN-843 Project: Infinispan Issue Type: Bug Components: Marshalling Affects Versions: 5.0.0.ALPHA1 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1 Externalizer config not correctly returned when using addExternalizer() API. It needs to take in account that an Externalizer instance might be set, and so retrieve id and externalizerClass info from it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2011