[JBoss JIRA] (ISPN-5769) Enabling/disabling partition handling action
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-5769?page=com.atlassian.jira.plugin.... ]
Pedro Zapata updated ISPN-5769:
-------------------------------
Description:
Per cache, enable or disable partition handling.
Note it’s a cache trait per cache, which should be very infrequently used. A label / icon will be displayed on the cache card to note a cache has not partition handling enabled. This shouldn’t be handled at the cache manager level.
It shouldn't be managed at the cache container level.
was:
As an Adminstrator, I want to enable Partition handling via at the Cache Container level: enabled or disabled.
Two options will be added to the cache container menu:
Enable partition handling
Disable partition handling
Shown in the menu at:
https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont...
> Enabling/disabling partition handling action
> --------------------------------------------
>
> Key: ISPN-5769
> URL: https://issues.jboss.org/browse/ISPN-5769
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Vladimir Blagojevic
>
> Per cache, enable or disable partition handling.
> Note it’s a cache trait per cache, which should be very infrequently used. A label / icon will be displayed on the cache card to note a cache has not partition handling enabled. This shouldn’t be handled at the cache manager level.
> It shouldn't be managed at the cache container level.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (ISPN-5809) View of cluster events
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-5809?page=com.atlassian.jira.plugin.... ]
Pedro Zapata updated ISPN-5809:
-------------------------------
Description:
As an Adminstrator, I want to view all cluster-split and cluster-merge events in the last 7 days. Each event should indicate the following information: time-stamp of event, Merge/Split, the cluster View before Merge/Split, the cluster View after Merge/Split.
Cluster events will be visualized as a summary in the cache containers page
https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont...
and in the cluster list page
https://rawgit.com/infinispan/infinispan-console-mockup/master/clusters.html
A detailed ‘Grid events’ page will be added:
https://rawgit.com/infinispan/infinispan-console-mockup/master/events.html
Type of logs:
* Task execution (as requested by users)
* Node join/leave
* Split/Merge
* Rebalancing start / stop
* Mass indexer
* Server start/shutdown
* Site up / down
* Cache related events
Log properties:
* Timestamp
* Title
* Description
Logs will be of severity INFO and ERROR.
Logs will be stored in a persistent, eviction, 7 days expiration cache.
was:
As an Adminstrator, I want to view all cluster-split and cluster-merge events in the last 7 days. Each event should indicate the following information: time-stamp of event, Merge/Split, the cluster View before Merge/Split, the cluster View after Merge/Split.
Other type of cluster related events need to be logged and shown in this screen.
> View of cluster events
> ----------------------
>
> Key: ISPN-5809
> URL: https://issues.jboss.org/browse/ISPN-5809
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Vladimir Blagojevic
>
> As an Adminstrator, I want to view all cluster-split and cluster-merge events in the last 7 days. Each event should indicate the following information: time-stamp of event, Merge/Split, the cluster View before Merge/Split, the cluster View after Merge/Split.
> Cluster events will be visualized as a summary in the cache containers page
> https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont...
> and in the cluster list page
> https://rawgit.com/infinispan/infinispan-console-mockup/master/clusters.html
> A detailed ‘Grid events’ page will be added:
> https://rawgit.com/infinispan/infinispan-console-mockup/master/events.html
> Type of logs:
> * Task execution (as requested by users)
> * Node join/leave
> * Split/Merge
> * Rebalancing start / stop
> * Mass indexer
> * Server start/shutdown
> * Site up / down
> * Cache related events
> Log properties:
> * Timestamp
> * Title
> * Description
> Logs will be of severity INFO and ERROR.
> Logs will be stored in a persistent, eviction, 7 days expiration cache.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (ISPN-5801) Cache with CacheLoader and CreatedExpiryPolicy Invalidates Instantly
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5801?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-5801:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/3733
> Cache with CacheLoader and CreatedExpiryPolicy Invalidates Instantly
> --------------------------------------------------------------------
>
> Key: ISPN-5801
> URL: https://issues.jboss.org/browse/ISPN-5801
> Project: Infinispan
> Issue Type: Bug
> Components: JCache
> Affects Versions: 8.0.1.Final
> Reporter: Dan Siviter
> Assignee: Galder Zamarreño
>
> When using a {{javax.cache.expiry.CreatedExpiryPolicy}} and a {{javax.cache.integration.CacheLoader}} the value generated for the {{org.infinispan.jcache.embedded/JCacheInternalMetadata#expiry}} is not relative to {{TimeService#wallClockTime}}. It therefore invalidates the entry instantly.
> I believe the problem is in {{org.infinispan.jcache.embedded.JCacheLoaderAdapter\[line=48\]}} where {{org.infinispan.jcache.Expiration#getExpiry(...)}} doesn't calculate the relative value so {{org.infinispan.jcache.embedded.JCacheInternalMetadata#isExpired}} always returns {{true}}.
> Unfortunately, work doesn't allow me to upload code so I can't submit an example.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (ISPN-5801) Cache with CacheLoader and CreatedExpiryPolicy Invalidates Instantly
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5801?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-5801:
-----------------------------------
Status: Open (was: New)
> Cache with CacheLoader and CreatedExpiryPolicy Invalidates Instantly
> --------------------------------------------------------------------
>
> Key: ISPN-5801
> URL: https://issues.jboss.org/browse/ISPN-5801
> Project: Infinispan
> Issue Type: Bug
> Components: JCache
> Affects Versions: 8.0.1.Final
> Reporter: Dan Siviter
> Assignee: Galder Zamarreño
>
> When using a {{javax.cache.expiry.CreatedExpiryPolicy}} and a {{javax.cache.integration.CacheLoader}} the value generated for the {{org.infinispan.jcache.embedded/JCacheInternalMetadata#expiry}} is not relative to {{TimeService#wallClockTime}}. It therefore invalidates the entry instantly.
> I believe the problem is in {{org.infinispan.jcache.embedded.JCacheLoaderAdapter\[line=48\]}} where {{org.infinispan.jcache.Expiration#getExpiry(...)}} doesn't calculate the relative value so {{org.infinispan.jcache.embedded.JCacheInternalMetadata#isExpired}} always returns {{true}}.
> Unfortunately, work doesn't allow me to upload code so I can't submit an example.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (ISPN-5822) Limit the number of expansion cofactors for hybrid query
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-5822:
-----------------------------------
Summary: Limit the number of expansion cofactors for hybrid query
Key: ISPN-5822
URL: https://issues.jboss.org/browse/ISPN-5822
Project: Infinispan
Issue Type: Enhancement
Components: Embedded Querying
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 8.1.0.Alpha2, 8.0.2.Final
When the are many non-indexed variables the boole-shannon expansion can become very large. In that case it's better to perform a full non-indexed search rather than a two-phase search. We need to be able to set a limit for the number of cofactors in the resulting product.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (ISPN-5187) Node.js HotRod client
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-5187?page=com.atlassian.jira.plugin.... ]
Pedro Zapata updated ISPN-5187:
-------------------------------
Description:
Either implement a pure javascript client or base on the native C++ client. Should be L2/L3 aware.
Initial scope:
* L1, L2, L3
* Async API (no sync API)
* Remote queries
* Remote Task execution
Target for 8.2+
* Remote events / listeners
* Cross site failover
* Security
* Encryption TLS
* Authentication SASL
was:Either implement a pure javascript client or base on the native C++ client. Should be L2/L3 aware.
> Node.js HotRod client
> ---------------------
>
> Key: ISPN-5187
> URL: https://issues.jboss.org/browse/ISPN-5187
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Protocols
> Reporter: Tristan Tarrant
> Assignee: Galder Zamarreño
> Fix For: 9.0.0.Final
>
>
> Either implement a pure javascript client or base on the native C++ client. Should be L2/L3 aware.
> Initial scope:
> * L1, L2, L3
> * Async API (no sync API)
> * Remote queries
> * Remote Task execution
> Target for 8.2+
> * Remote events / listeners
> * Cross site failover
> * Security
> * Encryption TLS
> * Authentication SASL
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months