[JBoss JIRA] (ISPN-5235) Implement node details page (P1)
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-5235?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic resolved ISPN-5235.
---------------------------------------
Release Notes Text: Obsolete task. UI specification has been changed
Resolution: Rejected
> Implement node details page (P1)
> --------------------------------
>
> Key: ISPN-5235
> URL: https://issues.jboss.org/browse/ISPN-5235
> Project: Infinispan
> Issue Type: Task
> Components: JMX, reporting and management
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 8.2.0.Alpha1
>
>
> In our admin console current node details page does not contain the following functionality that should be implemented:
> * All real-time metrics
> * -Cache list-
> * Cache filter
> * Node availability
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (ISPN-5234) Implement single cluster view page (P1)
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-5234?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic resolved ISPN-5234.
---------------------------------------
Release Notes Text: Specification changed. This task is obsolete
Resolution: Rejected
> Implement single cluster view page (P1)
> ---------------------------------------
>
> Key: ISPN-5234
> URL: https://issues.jboss.org/browse/ISPN-5234
> Project: Infinispan
> Issue Type: Task
> Components: JMX, reporting and management
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 8.2.0.Alpha1
>
>
> In our admin console current single cluster view page does not contain the following functionality that should be implemented:
> * -Zoom in/out-
> * Node availability/detail
> * Filter by metrics (node view)
> * Filter by metrics (cache view)
> * Search node (search as you type)
> * Search cache (search as you type)
> * -Cluster switcher-
> * Cluster status view
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (ISPN-6029) DDL for JDBC store tables should never allow null
by Paul Ferraro (JIRA)
Paul Ferraro created ISPN-6029:
----------------------------------
Summary: DDL for JDBC store tables should never allow null
Key: ISPN-6029
URL: https://issues.jboss.org/browse/ISPN-6029
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 8.0.2.Final, 8.1.0.Final
Reporter: Paul Ferraro
The DDL for jdbc persistent stores creates a 3 column table, where only the primary key is not null. However, both the string-based and binary-based cache stores require non-null values for the data column and timestamp column. These columns should not allow null values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (ISPN-3395) ISPN000196: Failed to recover cluster state after the current node became the coordinator
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3395?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3395:
-----------------------------------------------
Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1283465|https://bugzilla.redhat.com/show_bug.cgi?id=1283465] from MODIFIED to ON_QA
> ISPN000196: Failed to recover cluster state after the current node became the coordinator
> -----------------------------------------------------------------------------------------
>
> Key: ISPN-3395
> URL: https://issues.jboss.org/browse/ISPN-3395
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 5.3.0.Final
> Reporter: Mayank Agarwal
> Fix For: 6.0.2.Final, 7.0.0.Final, 5.2.16.Final
>
>
> We are using infinispan 5.3.0.Final in our distributed application. we are testing infinispan in HA scenarios and getting following exception when new node becomes co-ordinator.
> ISPN000196: Failed to recover cluster state after the current node became the coordinator
> java.lang.NullPointerException: null
> at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:455) ~[infinispan-core-5.3.0.1.Final.jar:5.3.0.1.Final]
> at org.infinispan.topology.ClusterTopologyManagerImpl.handleNewView(ClusterTopologyManagerImpl.java:235) ~[infinispan-core-5.3.0.1.Final.jar:5.3.0.1.Final]
> at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener$1.run(ClusterTopologyManagerImpl.java:647) ~[infinispan-core-5.3.0.1.Final.jar:5.3.0.1.Final]
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[na:1.6.0_25]
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) ~[na:1.6.0_25]
> at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.6.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [na:1.6.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.6.0_25]
> at java.lang.Thread.run(Unknown Source) [na:1.6.0_25]
> This is happening because cacheTopology is null at ClusterTopologyManagerImpl.java:455
> at 449: code is checking cacheTopology for null that for loop which is updating cacheStatusMap at 457 should be in that check itself.
> Fix:
> --- a/core/src/main/java/org/infinispan/topology/ClusterTopologyManagerImpl.java
> +++ b/core/src/main/java/org/infinispan/topology/ClusterTopologyManagerImpl.java
> @@ -448,7 +448,7 @@ public class ClusterTopologyManagerImpl implements ClusterTopologyManager {
> // but didn't get a response back yet
> if (cacheTopology != null) {
> topologyList.add(cacheTopology);
> - }
> +
>
> // Add all the members of the topology that have sent responses first
> // If we only added the sender, we could end up with a different member order
> @@ -457,6 +457,7 @@ public class ClusterTopologyManagerImpl implements ClusterTopologyManager {
> cacheStatusMap.get(cacheName).addMember(member);
> }
> }
> + }
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months