[JBoss JIRA] (ISPN-7745) clusterwide-hit-ratio returns NAN
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7745?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7745:
-------------------------------
Summary: clusterwide-hit-ratio returns NAN (was: clusterwide-hit-ration returns NAN)
> clusterwide-hit-ratio returns NAN
> ---------------------------------
>
> Key: ISPN-7745
> URL: https://issues.jboss.org/browse/ISPN-7745
> Project: Infinispan
> Issue Type: Bug
> Components: Console, JMX, reporting and management
> Affects Versions: 9.0.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 9.0.1.Final, 9.1.0.Alpha1
>
>
> "clusterwide-hit-ratio" statistic returns NaN in the DMR when a put operation occurs without any get operations, this causes the console to fail as it is unable to validate the NaN property in the subsequent JSON.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7745) clusterwide-hit-ration returns NAN
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7745?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7745:
-------------------------------
Component/s: Console
> clusterwide-hit-ration returns NAN
> ----------------------------------
>
> Key: ISPN-7745
> URL: https://issues.jboss.org/browse/ISPN-7745
> Project: Infinispan
> Issue Type: Bug
> Components: Console, JMX, reporting and management
> Affects Versions: 9.0.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: 9.0.1.Final, 9.1.0.Alpha1
>
>
> "clusterwide-hit-ratio" statistic returns NaN in the DMR when a put operation occurs without any get operations, this causes the console to fail as it is unable to validate the NaN property in the subsequent JSON.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7745) clusterwide-hit-ration returns NAN
by Ryan Emerson (JIRA)
Ryan Emerson created ISPN-7745:
----------------------------------
Summary: clusterwide-hit-ration returns NAN
Key: ISPN-7745
URL: https://issues.jboss.org/browse/ISPN-7745
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 9.0.0.Final
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 9.0.1.Final, 9.1.0.Alpha1
"clusterwide-hit-ratio" statistic returns NaN in the DMR when a put operation occurs without any get operations, this causes the console to fail as it is unable to validate the NaN property in the subsequent JSON.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7733) Administration console - Incorrect data field columns used on cache nodes page
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7733?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-7733:
-------------------------------------------
Ok, unless someone ([~NadirX] [~pzapataf] [~rmacor]) objects, I'll fix this issues by properly implementing TotalReads, TotalFailedReads, and TotalWrites as [~ryanemerson] and I have agreed. I'll omit TotalFailedWrites for now. We'll allow admins to customize these columns in the next iteration of stats page.
> Administration console - Incorrect data field columns used on cache nodes page
> ------------------------------------------------------------------------------
>
> Key: ISPN-7733
> URL: https://issues.jboss.org/browse/ISPN-7733
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Final
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.1.Final
>
> Attachments: Screen Shot 2017-04-19 at 5.55.58 AM.png
>
>
> We've been using average-read-time value in place for TotalReads, TotalFailedReads, TotalWrites, and TotalFailedWrites. Since we do not have the data for TotalReads, TotalFailedReads, TotalWrites, and TotalFailedWrites we need to replace these four fields with some of the following:
> number-of-entries
> number-of-entries-in-memory
> average-remove-time
> number-of-locks-available
> average-replication-time
> number-of-locks-held
> average-write-time
> off-heap-memory-used
> passivations
> cache-loader-loads
> prepares
> cache-loader-misses
> read-write-ratio
> cache-loader-stores
> remove-hits
> remove-misses
> replication-count
> replication-failures
> rollbacks
> commits
> stores
> success-ratio
> evictions
> hit-ratio
> hits
> Let's pick 4-6 most useful fields and we'll enable admins to choose their own stat fields in subsequent versions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7744) ServerEventLoggerTest.testLocalServerEventLogging fails intermittently
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7744?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant moved JDG-963 to ISPN-7744:
-------------------------------------------
Project: Infinispan (was: JBoss Data Grid)
Key: ISPN-7744 (was: JDG-963)
Workflow: GIT Pull Request with Triage workflow (was: CDW with loose statuses v1)
Component/s: Test Suite - Server
(was: TestSuite)
Affects Version/s: 9.0.0.Final
(was: JDG 7.1.0 ER7)
> ServerEventLoggerTest.testLocalServerEventLogging fails intermittently
> ----------------------------------------------------------------------
>
> Key: ISPN-7744
> URL: https://issues.jboss.org/browse/ISPN-7744
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 9.0.0.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
>
> I got org.infinispan.server.eventlogger.ServerEventLoggerTest.testLocalServerEventLogging fail on Windows with following stacktrace:
> {code}
> java.lang.AssertionError: expected:<2> but was:<1>
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
> at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252)
> at org.infinispan.server.eventlogger.ServerEventLoggerTest$1.call(ServerEventLoggerTest.java:60)
> at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1296)
> at org.infinispan.server.eventlogger.ServerEventLoggerTest.testLocalServerEventLogging(ServerEventLoggerTest.java:43)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-6766) hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6766?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6766:
----------------------------------
Fix Version/s: 8.2.7.Final
> hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6766
> URL: https://issues.jboss.org/browse/ISPN-6766
> Project: Infinispan
> Issue Type: Bug
> Components: Listeners, Remote Protocols
> Affects Versions: 8.2.1.Final
> Reporter: Eli Z
> Assignee: Katia Aresti
> Priority: Minor
> Fix For: 9.1.0.Final, 8.2.7.Final, 9.0.1.Final, 9.1.0.Alpha1
>
>
> After registering a client listener in the client and then restarting the infinispan server --> The original listener object can not be removed from the client listener list by using the method RemoteCache.removeClient(Object listener) --> after calling this method and then get all listeners, i still see the old listener in the list.
> By doing a little debug, it seems that in class RemoveClientListenerOperation.execute when trying to remove from the server and a failure status is returned (probably due to the fact the the server after the restart does not know this listener id) the listener is not removed from the list eventually. the line this.listenerNotifier.removeClientListener(listenerId); is not executed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-6766) hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6766?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6766:
----------------------------------
Fix Version/s: 9.0.1.Final
9.1.0.Alpha1
> hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6766
> URL: https://issues.jboss.org/browse/ISPN-6766
> Project: Infinispan
> Issue Type: Bug
> Components: Listeners, Remote Protocols
> Affects Versions: 8.2.1.Final
> Reporter: Eli Z
> Assignee: Katia Aresti
> Priority: Minor
> Fix For: 9.1.0.Final, 8.2.7.Final, 9.0.1.Final, 9.1.0.Alpha1
>
>
> After registering a client listener in the client and then restarting the infinispan server --> The original listener object can not be removed from the client listener list by using the method RemoteCache.removeClient(Object listener) --> after calling this method and then get all listeners, i still see the old listener in the list.
> By doing a little debug, it seems that in class RemoveClientListenerOperation.execute when trying to remove from the server and a failure status is returned (probably due to the fact the the server after the restart does not know this listener id) the listener is not removed from the list eventually. the line this.listenerNotifier.removeClientListener(listenerId); is not executed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-6766) hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6766?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6766:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6766
> URL: https://issues.jboss.org/browse/ISPN-6766
> Project: Infinispan
> Issue Type: Bug
> Components: Listeners, Remote Protocols
> Affects Versions: 8.2.1.Final
> Reporter: Eli Z
> Assignee: Katia Aresti
> Priority: Minor
> Fix For: 9.1.0.Final, 9.0.1.Final, 9.1.0.Alpha1
>
>
> After registering a client listener in the client and then restarting the infinispan server --> The original listener object can not be removed from the client listener list by using the method RemoteCache.removeClient(Object listener) --> after calling this method and then get all listeners, i still see the old listener in the list.
> By doing a little debug, it seems that in class RemoveClientListenerOperation.execute when trying to remove from the server and a failure status is returned (probably due to the fact the the server after the restart does not know this listener id) the listener is not removed from the list eventually. the line this.listenerNotifier.removeClientListener(listenerId); is not executed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months