[JBoss JIRA] (ISPN-4924) CacheEntryEvent isOriginLocal is not correct in many circumstances
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-4924?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-4924:
--------------------------------
Fix Version/s: 7.2.0.Beta1
(was: 7.2.0.Alpha1)
> CacheEntryEvent isOriginLocal is not correct in many circumstances
> ------------------------------------------------------------------
>
> Key: ISPN-4924
> URL: https://issues.jboss.org/browse/ISPN-4924
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 7.0.0.CR2
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 7.2.0.Beta1
>
>
> Origin local flag was messed up when nontx DIST was rewritten to have the primary owner send updates to the backup nodes. This in turn affected REPL when it was changed to be implemented on top of DIST. I believe that tx is unaffected. Also new cluster listeners don't put the flag properly for DIST caches if the originator is not also the primary owner.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (ISPN-5012) ClusterRegistry as a service cache provider
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-5012?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-5012:
--------------------------------
Fix Version/s: 7.2.0.Beta1
(was: 7.2.0.Alpha1)
> ClusterRegistry as a service cache provider
> -------------------------------------------
>
> Key: ISPN-5012
> URL: https://issues.jboss.org/browse/ISPN-5012
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 7.2.0.Beta1
>
>
> The ClusterRegistry is currently a volatile, replicated cache with a composite key and it does not serve the original purpose for which it was built. It should be refactored to be a service cache factory with a builder API based on desired features and a NamingStrategy so that we can have "well-known" caches as well as temporary caches. It should also be possible to use the cache dependency mechanism to "chain" service cache lifecycles to other caches.
> Here's an example API (not a real example):
> RegistryBuilder builder = registry.getBuilder();
> builder.persistent().clustered().dependsOn(Cache<?,?> cache).namingStrategy(new StaticCacheNamingStrategy("___protobuf_metadata"))
> This registry would be able to provide caches to the following use cases:
> - protobuf schemas
> - hotrod topology
> - security acl
> - map/reduce work caches
> - index caches
> - etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (ISPN-5013) Server-side scripting using JSR-223 (javax.script)
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-5013?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-5013:
--------------------------------
Fix Version/s: 7.2.0.Beta1
(was: 7.2.0.Alpha1)
> Server-side scripting using JSR-223 (javax.script)
> --------------------------------------------------
>
> Key: ISPN-5013
> URL: https://issues.jboss.org/browse/ISPN-5013
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Server
> Affects Versions: 7.0.2.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 7.2.0.Beta1
>
>
> Implement a scripting manager which stores custom scripts in a dedicated cache. These scripts will be invoked with a user-specified binding (i.e. a set of named parameters).
> This component should support all known "code" extension points: simple, tasks, distexec, map/reduce, listeners, etc.
> The script type should be supported by the available JSR-223 scripting engines
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (ISPN-5010) Improve remote listener performance
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-5010?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-5010:
--------------------------------
Fix Version/s: 7.2.0.Beta1
(was: 7.2.0.Alpha1)
> Improve remote listener performance
> -----------------------------------
>
> Key: ISPN-5010
> URL: https://issues.jboss.org/browse/ISPN-5010
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Protocols
> Affects Versions: 7.0.2.Final
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 7.2.0.Beta1
>
>
> We've run some performance tests and we've noticed remote listeners have a too negative effect on get/put/remove operations, particularly as number of listeners added by clients increase. This JIRA encompasses different pieces of work to improve this:
> * Make server-side clustered listener async. By doing so, the operations are detached from the actual server-side listener part when the notification is sent to clients. Async listener executor is configured with 1 thread, so order is still maintained.
> * Batching at the server-side clustered listener side. Instead of sending each event as it comes, apply time/size based batching to reduce number of system calls to flush sockets to clients.
> * Further improvements might come from bundling listeners added by same client, but this is more complicated to achieve, since only those listeners that have similar characteristics can be bundled, e.g. have same filter/converter settings. Also, whether to use a single connection for all listeners or maintain separate ones still would need to be decided. (see ISPN-4491)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months