[JBoss JIRA] (ISPN-1893) Query module demo
by Mathieu Lachance (JIRA)
Mathieu Lachance created ISPN-1893:
--------------------------------------
Summary: Query module demo
Key: ISPN-1893
URL: https://issues.jboss.org/browse/ISPN-1893
Project: Infinispan
Issue Type: Task
Components: Core API, Locking and Concurrency, Migration tools
Reporter: Mathieu Lachance
Assignee: Manik Surtani
Would it be possible to make a query-module demo showing the best practice with :
- replication clustering mode + local query,
- distribution clustering mode + index replication + local query,
- distribution clustering mode + clustered query
I guess this would be easy to integrate it in the already existant gui demo.
Big thanks !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (ISPN-2082) JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values > 4000 bytes
by Ryan Scharer (JIRA)
Ryan Scharer created ISPN-2082:
----------------------------------
Summary: JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values > 4000 bytes
Key: ISPN-2082
URL: https://issues.jboss.org/browse/ISPN-2082
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.5.FINAL
Environment: OS X 10.7.4, JDK 1.7.0u4
Reporter: Ryan Scharer
Assignee: Manik Surtani
I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything works fine. If the value is greater, the cache store fails with ORA-24816. This occurs because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore implementation and write my own insert/update SQL in storeLockSafe(). This works fine, but obviously isn't ideal from an upgrade point of view. Simply overriding storeLockSafe() isn't an option due to all the private fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] Created: (ISPN-1403) Optimise sending Hot Rod topology updates for distributed caches
by Galder Zamarreño (JIRA)
Optimise sending Hot Rod topology updates for distributed caches
----------------------------------------------------------------
Key: ISPN-1403
URL: https://issues.jboss.org/browse/ISPN-1403
Project: Infinispan
Issue Type: Enhancement
Components: Cache Server, Distributed Cache
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
Right now, whenever a Hot Rod client sends a request with a view id which is different to the one on the server, it'd get a brand new view in the response to the request. This could be optimised nicely by only sending back a new view id when the server discovers that the client is using an inefficient view. For example, in distributed caches, the moment it gets a request for a key which lands on a node that does not own the key, it could decide to send back the view.
This would reduce the number of times the view is returned, hence improving the performance of requests.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (ISPN-1534) Optimise Hot Rod client and server to work with asynchronous distributed caches
by Galder Zamarreño (Created) (JIRA)
Optimise Hot Rod client and server to work with asynchronous distributed caches
-------------------------------------------------------------------------------
Key: ISPN-1534
URL: https://issues.jboss.org/browse/ISPN-1534
Project: Infinispan
Issue Type: Feature Request
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
With Hot Rod clients, we can control where to direct invocations too, so there's a very interesting performance optimization we can apply with distributed caches. We can tolerate, and benefit from the speed of, asynchronous distributed caches very easily if we can get Hot Rod clients to always hit the owner of a key.
It's a bit like sticky sessions, but applied to remote distributed caches! I think this would improve performance of our Hot Rod architecture quite notably.
I think the Hot Rod client already works this way since I don't think it load balances between owners of a key.
So, the aim of this JIRA is to:
1. Verify whether the Hot Rod client works this way
2. Consider whether Hot Rod servers could transform, on the fly, synchronous distributed caches into asynchronous ones, indicating so in the logs (INFO level).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months