[JBoss JIRA] (ISPN-6777) Improve Cache Stores configuration screen
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-6777?page=com.atlassian.jira.plugin.... ]
Pedro Zapata updated ISPN-6777:
-------------------------------
Fix Version/s: 9.0.0.Beta2
> Improve Cache Stores configuration screen
> -----------------------------------------
>
> Key: ISPN-6777
> URL: https://issues.jboss.org/browse/ISPN-6777
> Project: Infinispan
> Issue Type: Feature Request
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.0.Beta2
>
>
> Infinispan administrators should be able to select and configure any cache store easily, without having to enter class names and other free-form properties.
> Only one tab ‘Cache store’ will be displayed in the cache configuration options
> The user will have the option to select a type of store from the list (Single File, LevelDB, …) + the option ‘NONE’
> When the option is changed, all the generic + specific properties will be shown below.
> Properties should be presented as combos, if they are enumerable. For example, class (if there’s a way of filtering all implementing classes in classpath).
> Sensible defaults should be set.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6782) Add connectivity lost warning message
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-6782?page=com.atlassian.jira.plugin.... ]
Pedro Zapata updated ISPN-6782:
-------------------------------
Fix Version/s: 9.0.0.Beta1
> Add connectivity lost warning message
> -------------------------------------
>
> Key: ISPN-6782
> URL: https://issues.jboss.org/browse/ISPN-6782
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.0.Beta1
>
>
> If the app loses connection to the backend server, it should trigger a warning message to the user, regardless the screen he is in. This service must be general and consistent across the whole application, and provide almost immediate feedback connectivity has been lost.
> Toast notifications can be used for this. It’ll be notified to the user immediately if connection to the server is lost. This can work either when trying to connect (handling an error) or with a periodic ping of every 5 secs if the application is idle.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6809) Monitor indexing status
by Pedro Zapata (JIRA)
Pedro Zapata created ISPN-6809:
----------------------------------
Summary: Monitor indexing status
Key: ISPN-6809
URL: https://issues.jboss.org/browse/ISPN-6809
Project: Infinispan
Issue Type: Enhancement
Components: Console
Reporter: Pedro Zapata
Assignee: Vladimir Blagojevic
Status of mass indexer and index status should be displayed per cache.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6808) Validation of properties and detailed error feedback
by Pedro Zapata (JIRA)
Pedro Zapata created ISPN-6808:
----------------------------------
Summary: Validation of properties and detailed error feedback
Key: ISPN-6808
URL: https://issues.jboss.org/browse/ISPN-6808
Project: Infinispan
Issue Type: Enhancement
Components: Console
Reporter: Pedro Zapata
Assignee: Vladimir Blagojevic
Form fields must be validated to prevent inconsistent configurations that could prevent the server be restarted because of a config validation error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6807) Customization of console features by configuration
by Pedro Zapata (JIRA)
Pedro Zapata created ISPN-6807:
----------------------------------
Summary: Customization of console features by configuration
Key: ISPN-6807
URL: https://issues.jboss.org/browse/ISPN-6807
Project: Infinispan
Issue Type: Enhancement
Components: Console
Reporter: Pedro Zapata
Assignee: Vladimir Blagojevic
A simpler, centralized way of customizing ISPN console is required, without relying on forking the code. This needs to allow for disabling / hiding some features or properties that are not supported in product.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6806) Exception serializing L1InternalCacheEntry during state transfer
by Dan Berindei (JIRA)
Dan Berindei created ISPN-6806:
----------------------------------
Summary: Exception serializing L1InternalCacheEntry during state transfer
Key: ISPN-6806
URL: https://issues.jboss.org/browse/ISPN-6806
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 8.2.2.Final, 9.0.0.Alpha2, 7.2.5.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 9.0.0.Final
{{L1InternalCacheEntry}} is not serializable, as only entries properly owned by the node are supposed to be sent via state transfer.
However, when the last owner of a segment leaves the cluster, one of the other nodes becomes the owner of that segment, and the L1 entries it already has suddenly become part of the state it can send to other nodes. It then fails to send its state with this exception:
{noformat}
[org.infinispan.marshall.core.VersionAwareMarshaller] (transport-thread--p19-t14) Object is not serializable: java.io.NotSerializableException: org.infinispan.container.entries.L1InternalCacheEntry
{noformat}
This can happen quite often if L1 is enabled and {{numOwners = 1}}.
Unfortunately, the serialization exception isn't propagated, and all the user sees is an initial state transfer timeout exception when trying to start another node later.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6647) DecoratedCache.putForExternalRead method with Metadata ignores Metadata
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-6647?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek reassigned ISPN-6647:
-------------------------------------
Assignee: Karl von Randow
> DecoratedCache.putForExternalRead method with Metadata ignores Metadata
> -----------------------------------------------------------------------
>
> Key: ISPN-6647
> URL: https://issues.jboss.org/browse/ISPN-6647
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 8.2.2.Final
> Reporter: Karl von Randow
> Assignee: Karl von Randow
> Priority: Minor
>
> The implementation of the {{putForExternalRead}} method ignores the {{Metadata}} parameter, instead of passing it on to the {{putForExternalRead}} method in the cache implementation. This is no doubt because the cache implementation previously didn't support {{Metadata}} for {{putForExternalRead}}.
> I will prepare a PR and attach it to this ticket shortly. It was a gargantuan effort to patch this up, as you'll see!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ISPN-6647) DecoratedCache.putForExternalRead method with Metadata ignores Metadata
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-6647?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek updated ISPN-6647:
----------------------------------
Status: Open (was: New)
> DecoratedCache.putForExternalRead method with Metadata ignores Metadata
> -----------------------------------------------------------------------
>
> Key: ISPN-6647
> URL: https://issues.jboss.org/browse/ISPN-6647
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 8.2.2.Final
> Reporter: Karl von Randow
> Assignee: Karl von Randow
> Priority: Minor
>
> The implementation of the {{putForExternalRead}} method ignores the {{Metadata}} parameter, instead of passing it on to the {{putForExternalRead}} method in the cache implementation. This is no doubt because the cache implementation previously didn't support {{Metadata}} for {{putForExternalRead}}.
> I will prepare a PR and attach it to this ticket shortly. It was a gargantuan effort to patch this up, as you'll see!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months