[JBoss JIRA] (ISPN-8434) Management console should write/read time unit and adjust it
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-8434:
--------------------------------------
Summary: Management console should write/read time unit and adjust it
Key: ISPN-8434
URL: https://issues.jboss.org/browse/ISPN-8434
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 9.1.0.Final
Reporter: Galder Zamarreño
Attachments: Screen Shot 2017-10-18 at 17.06.21.png
The management console is showing me that the average write took 593,036... what? See screenshot
Not only should it mention the unit, but it should adjust it. The JMX API exposes the number of nanoseconds, which is most likely not very relevant... in this case, 593ms might be more relevant... but it should adjust it so that it makes some sense to the reader.
As a side note: averages don't mean much, but that's a different topic ;)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8434) Management console should write/read time unit and adjust it
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-8434?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-8434:
-----------------------------------
Attachment: Screen Shot 2017-10-18 at 17.06.21.png
> Management console should write/read time unit and adjust it
> ------------------------------------------------------------
>
> Key: ISPN-8434
> URL: https://issues.jboss.org/browse/ISPN-8434
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.1.0.Final
> Reporter: Galder Zamarreño
> Attachments: Screen Shot 2017-10-18 at 17.06.21.png
>
>
> The management console is showing me that the average write took 593,036... what? See screenshot
> Not only should it mention the unit, but it should adjust it. The JMX API exposes the number of nanoseconds, which is most likely not very relevant... in this case, 593ms might be more relevant... but it should adjust it so that it makes some sense to the reader.
> As a side note: averages don't mean much, but that's a different topic ;)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8433) Cache counts per node in management console incorrect
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-8433?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-8433:
-----------------------------------
Attachment: Screen Shot 2017-10-18 at 17.05.10.png
> Cache counts per node in management console incorrect
> -----------------------------------------------------
>
> Key: ISPN-8433
> URL: https://issues.jboss.org/browse/ISPN-8433
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.1.0.Final
> Reporter: Galder Zamarreño
> Attachments: Screen Shot 2017-10-18 at 17.05.10.png
>
>
> I was playing around with the management console, and the write counts per node in a cache don't appear to be correct. The count per node seems to be evaluated from the total, divided by number of nodes, but in a distributed cache that's not exactly true. Each node might have slightly different count.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8433) Cache counts per node in management console incorrect
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-8433:
--------------------------------------
Summary: Cache counts per node in management console incorrect
Key: ISPN-8433
URL: https://issues.jboss.org/browse/ISPN-8433
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 9.1.0.Final
Reporter: Galder Zamarreño
I was playing around with the management console, and the write counts per node in a cache don't appear to be correct. The count per node seems to be evaluated from the total, divided by number of nodes, but in a distributed cache that's not exactly true. Each node might have slightly different count.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8432) TopologyChangeFunctionalTest.testOriginatorLeft fails randomly
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8432?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8432:
----------------------------------
Description:
http://ci.infinispan.org/job/Infinispan/job/PR-5506/3/testReport/junit/or...
java.lang.AssertionError: Status should have been 'Success' but instead was: 'KeyDoesNotExist'
at org.infinispan.server.hotrod.test.HotRodTestingUtil.assertStatus(HotRodTestingUtil.java:265)
at org.infinispan.server.hotrod.test.HotRodTestingUtil.assertSuccess(HotRodTestingUtil.java:271)
at org.infinispan.server.hotrod.tx.TopologyChangeFunctionalTest.assertData(TopologyChangeFunctionalTest.java:227)
at org.infinispan.server.hotrod.tx.TopologyChangeFunctionalTest.testOriginatorLeft(TopologyChangeFunctionalTest.java:126)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
... Removed 18 stack frames
was:
java.lang.AssertionError: Status should have been 'Success' but instead was: 'KeyDoesNotExist'
at org.infinispan.server.hotrod.test.HotRodTestingUtil.assertStatus(HotRodTestingUtil.java:265)
at org.infinispan.server.hotrod.test.HotRodTestingUtil.assertSuccess(HotRodTestingUtil.java:271)
at org.infinispan.server.hotrod.tx.TopologyChangeFunctionalTest.assertData(TopologyChangeFunctionalTest.java:227)
at org.infinispan.server.hotrod.tx.TopologyChangeFunctionalTest.testOriginatorLeft(TopologyChangeFunctionalTest.java:126)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
... Removed 18 stack frames
> TopologyChangeFunctionalTest.testOriginatorLeft fails randomly
> --------------------------------------------------------------
>
> Key: ISPN-8432
> URL: https://issues.jboss.org/browse/ISPN-8432
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 9.2.0.Alpha1
> Environment: Jenkins
> Reporter: Tristan Tarrant
> Assignee: Pedro Ruivo
> Labels: testsuite_stability
>
> http://ci.infinispan.org/job/Infinispan/job/PR-5506/3/testReport/junit/or...
> java.lang.AssertionError: Status should have been 'Success' but instead was: 'KeyDoesNotExist'
> at org.infinispan.server.hotrod.test.HotRodTestingUtil.assertStatus(HotRodTestingUtil.java:265)
> at org.infinispan.server.hotrod.test.HotRodTestingUtil.assertSuccess(HotRodTestingUtil.java:271)
> at org.infinispan.server.hotrod.tx.TopologyChangeFunctionalTest.assertData(TopologyChangeFunctionalTest.java:227)
> at org.infinispan.server.hotrod.tx.TopologyChangeFunctionalTest.testOriginatorLeft(TopologyChangeFunctionalTest.java:126)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ... Removed 18 stack frames
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (ISPN-8432) TopologyChangeFunctionalTest.testOriginatorLeft fails randomly
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-8432:
-------------------------------------
Summary: TopologyChangeFunctionalTest.testOriginatorLeft fails randomly
Key: ISPN-8432
URL: https://issues.jboss.org/browse/ISPN-8432
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Server
Affects Versions: 9.2.0.Alpha1
Environment: Jenkins
Reporter: Tristan Tarrant
Assignee: Pedro Ruivo
java.lang.AssertionError: Status should have been 'Success' but instead was: 'KeyDoesNotExist'
at org.infinispan.server.hotrod.test.HotRodTestingUtil.assertStatus(HotRodTestingUtil.java:265)
at org.infinispan.server.hotrod.test.HotRodTestingUtil.assertSuccess(HotRodTestingUtil.java:271)
at org.infinispan.server.hotrod.tx.TopologyChangeFunctionalTest.assertData(TopologyChangeFunctionalTest.java:227)
at org.infinispan.server.hotrod.tx.TopologyChangeFunctionalTest.testOriginatorLeft(TopologyChangeFunctionalTest.java:126)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
... Removed 18 stack frames
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months