[JBoss JIRA] Created: (ISPN-200) Distributed queries
by Manik Surtani (JIRA)
Distributed queries
-------------------
Key: ISPN-200
URL: https://jira.jboss.org/jira/browse/ISPN-200
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache, Querying
Reporter: Manik Surtani
Assignee: Manik Surtani
Fix For: 5.1.0.BETA1, 5.1.0.GA
The holy grail of querying.
* Indexes are _never_ shared.
* Each node maintains local indexes for state it is responsible
for (-Dinfinispan.query.indexLocalOnly=true).
* Indexes could be in memory or disk.
* Queries themselves are distributed.
* The query object is built and broadcast to the entire cluster.
* Each node executes the query on its own _local_ index, returning
results.
* The calling node returns a CacheQuery impl that lazily fetches
and collates results from the cluster.
* I expect this Map/Reduce model to perform very well since the
workload is split up and happens in parallel across multiple CPUs
against much smaller (individual) datasets.
* Works with all cache modes, including DIST.
* Need to make sure duplicates are handled, as well as failover.
--
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
13 years, 3 months
[JBoss JIRA] Created: (ISPN-813) "Infinispan Cache Manager" option doesn't show up in the drop down menu for "Manually add" function
by Michal Linhard (JIRA)
"Infinispan Cache Manager" option doesn't show up in the drop down menu for "Manually add" function
---------------------------------------------------------------------------------------------------
Key: ISPN-813
URL: https://jira.jboss.org/browse/ISPN-813
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 4.2.0.CR2
Reporter: Michal Linhard
Assignee: Manik Surtani
infinispan 4.2.0.CR2
RHQ version: 3.0.0 build number: 59e9341
postgresql 8.4.5
I've setup RHQ with infinispan-jopr-plugin as described here:
http://community.jboss.org/wiki/MonitoringInfinispanwithRHQ
I'm running this on my local machine having these virtual interfaces
192.168.10.101 test1
192.168.10.102 test2
192.168.10.103 test3
192.168.10.104 test4
192.168.10.105 test5
192.168.10.106 test6
test1 - test4 running jboss 5.1.0.GA with infinispan-gridfs-webdav demo (ran with -Dcom.sun.management.jmxremote.port=6991 to 9664 respectively)
test1 - test2 running rhq-agent bound to respective interface
test5 running rhq-server
sucessfully installed RHQ server
sucessfully installed agents test1 test2
sucessfully imported platforms test1 and test2
sucessfully installed infinispan-jopr-plugin, updated agents
tried to manually add Infinispan Cache Manager according to the instructions:
"To add Infinispan instances manually, go to Resources > Platforms > localhost and then click on Inventory. At the bottom of the page, there's a section that says "Manually Add" and next to it there's a drop down list. Open this list, select "Infinispan Cache Manager" and click Ok."
but the option "Infinispan Cache Manager" doesn't appear in the drop down box.
i don't know wheter this is a RHQ bug or plugin bug or wheter there's something wrong with my installation steps.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (ISPN-359) Affinity accross caches - static or dynamic
by Tero Heinonen (JIRA)
Affinity accross caches - static or dynamic
-------------------------------------------
Key: ISPN-359
URL: https://jira.jboss.org/jira/browse/ISPN-359
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Cache
Affects Versions: 4.0.0.Final
Reporter: Tero Heinonen
Assignee: Manik Surtani
Programmable affinity either through:
1) statically (e.g. annotating a certain field as the key for consistent hashing)
- in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related
2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function)
This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups)
--
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
13 years, 5 months