April 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7746) Administration console - clear statistics action is not wired on General Status cache page

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-7746: ----------------------------------------- Summary: Administration console - clear statistics action is not wired on General Status cache page Key: ISPN-7746 URL: https://issues.jboss.org/browse/ISPN-7746 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 We have wired reset stats on Nodes cache page but not on General Status page as well. When admin invokes "Reset statistics" on General Status page statistics are not reset. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7746) Administration console - reset statistics action is not wired on General Status cache page

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7746?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7746: -------------------------------------- Summary: Administration console - reset statistics action is not wired on General Status cache page (was: Administration console - clear statistics action is not wired on General Status cache page) > Administration console - reset statistics action is not wired on General Status cache page > ------------------------------------------------------------------------------------------ > > Key: ISPN-7746 > URL: https://issues.jboss.org/browse/ISPN-7746 > 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 > > > We have wired reset stats on Nodes cache page but not on General Status page as well. When admin invokes "Reset statistics" on General Status page statistics are not reset. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7479) Add Failover and Execution Policy to ClusterExecutor

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7479?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7479: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5092 > Add Failover and Execution Policy to ClusterExecutor > ---------------------------------------------------- > > Key: ISPN-7479 > URL: https://issues.jboss.org/browse/ISPN-7479 > Project: Infinispan > Issue Type: Enhancement > Components: Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 9.1.0.Alpha1 > > > The ClusterExecutor interface was added in Infinispan 8 to allow for a user to run commands without a cache (just cache manager). This is very similar to DistributedExecutor. However DistributedExecutor also had policies for failover and execution. We should add this functionality to ClusterExecutor as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7479) Add Failover and Execution Policy to ClusterExecutor

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7479?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7479: -------------------------------- Fix Version/s: 9.1.0.Alpha1 > Add Failover and Execution Policy to ClusterExecutor > ---------------------------------------------------- > > Key: ISPN-7479 > URL: https://issues.jboss.org/browse/ISPN-7479 > Project: Infinispan > Issue Type: Enhancement > Components: Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 9.1.0.Alpha1 > > > The ClusterExecutor interface was added in Infinispan 8 to allow for a user to run commands without a cache (just cache manager). This is very similar to DistributedExecutor. However DistributedExecutor also had policies for failover and execution. We should add this functionality to ClusterExecutor as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[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 updated ISPN-7733: -------------------------------------- Status: Open (was: New) > 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)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7743) DistributedStreamIteratorTest.testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues fails randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7743?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7743: ------------------------------- Description: testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues waits for rehash to complete. If this is slow for some reason it can cause the rest of the test to time out. There is no reason for the test itself to wait for the rehash as the stream operation should handle this automatically anyways. {noformat} java.lang.IllegalStateException: Thread already timed out waiting for event pre_iterator_released at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:131) at org.infinispan.test.fwk.CheckPoint.triggerForever(CheckPoint.java:120) at org.infinispan.stream.DistributedStreamIteratorTest.testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues(DistributedStreamIteratorTest.java:249) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {noformat} was:testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues waits for rehash to complete. If this is slow for some reason it can cause the rest of the test to time out. There is no reason for the test itself to wait for the rehash as the stream operation should handle this automatically anyways. > DistributedStreamIteratorTest.testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues fails randomly > --------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7743 > URL: https://issues.jboss.org/browse/ISPN-7743 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.1.0.Final, 9.1.0.Alpha1 > > > testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues waits for rehash to complete. If this is slow for some reason it can cause the rest of the test to time out. There is no reason for the test itself to wait for the rehash as the stream operation should handle this automatically anyways. > {noformat} > java.lang.IllegalStateException: Thread already timed out waiting for event pre_iterator_released > at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:131) > at org.infinispan.test.fwk.CheckPoint.triggerForever(CheckPoint.java:120) > at org.infinispan.stream.DistributedStreamIteratorTest.testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues(DistributedStreamIteratorTest.java:249) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7743) DistributedStreamIteratorTest.testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues fails randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7743?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7743: ------------------------------- Fix Version/s: 9.1.0.Alpha1 > DistributedStreamIteratorTest.testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues fails randomly > --------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7743 > URL: https://issues.jboss.org/browse/ISPN-7743 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.1.0.Final, 9.1.0.Alpha1 > > > testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues waits for rehash to complete. If this is slow for some reason it can cause the rest of the test to time out. There is no reason for the test itself to wait for the rehash as the stream operation should handle this automatically anyways. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7743) DistributedStreamIteratorTest.testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues fails randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7743?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7743: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > DistributedStreamIteratorTest.testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues fails randomly > --------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7743 > URL: https://issues.jboss.org/browse/ISPN-7743 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.1.0.Final > > > testNodeLeavesWhileIteratingOverContainerCausingRehashToLoseValues waits for rehash to complete. If this is slow for some reason it can cause the rest of the test to time out. There is no reason for the test itself to wait for the rehash as the stream operation should handle this automatically anyways. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[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)

7 years, 1 month

1
0
0 / 0

[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)

7 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2017