January 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8664) UI improvements in Template Configuration

by Diego Lovison (JIRA)

Diego Lovison created ISPN-8664: ----------------------------------- Summary: UI improvements in Template Configuration Key: ISPN-8664 URL: https://issues.jboss.org/browse/ISPN-8664 Project: Infinispan Issue Type: Feature Request Components: Console Affects Versions: 9.2.0.Beta2 Reporter: Diego Lovison Priority: Trivial 1. Start the Infinispan server in the standalone mode using the clustered option. Command to be executed: ./standalone.sh -Djboss.socket.binding.port-offset=100 -Djboss.node.name=nodeA -c clustered.xml 2. Open http://127.0.0.1:10090/console/index.html#/containers/standalone/clustere... and hit the button “Create new template”. Fill the information and hit the “Next” button. 3. In the "Clustering" panel you will see that there are values in the fields: Owners, Segments, L1 Lifespan, etc. 4. Hit the “Create” button. The new template will appears in the list. 5. In the list, hit the “Edit” button 6. You will see that the values are empty. I am expecting the same values when I was creating the Template Configuration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8664) UX improvements in Template Configuration

by Diego Lovison (JIRA)

[ https://issues.jboss.org/browse/ISPN-8664?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-8664: -------------------------------- Summary: UX improvements in Template Configuration (was: UI improvements in Template Configuration) > UX improvements in Template Configuration > ----------------------------------------- > > Key: ISPN-8664 > URL: https://issues.jboss.org/browse/ISPN-8664 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 9.2.0.Beta2 > Reporter: Diego Lovison > Priority: Trivial > > 1. Start the Infinispan server in the standalone mode using the clustered option. Command to be executed: ./standalone.sh -Djboss.socket.binding.port-offset=100 -Djboss.node.name=nodeA -c clustered.xml > 2. Open http://127.0.0.1:10090/console/index.html#/containers/standalone/clustere... and hit the button “Create new template”. Fill the information and hit the “Next” button. > 3. In the "Clustering" panel you will see that there are values in the fields: Owners, Segments, L1 Lifespan, etc. > 4. Hit the “Create” button. The new template will appears in the list. > 5. In the list, hit the “Edit” button > 6. You will see that the values are empty. I am expecting the same values when I was creating the Template Configuration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8663) The log is swapping the name and template

by Diego Lovison (JIRA)

Diego Lovison created ISPN-8663: ----------------------------------- Summary: The log is swapping the name and template Key: ISPN-8663 URL: https://issues.jboss.org/browse/ISPN-8663 Project: Infinispan Issue Type: Enhancement Components: Core Affects Versions: 9.2.0.Beta2 Reporter: Diego Lovison Priority: Minor Create a Java Class that access the cluster configuration using the Hot Rod protocol and execute the following code: RemoteCache<Object, Object> cache = rmc.administration().getOrCreateCache("my-cache", "template-example"); It will return: “ISPN000374: No such template ‘my-cache’ when declaring 'template-example' To reproduce this issue the "template-example" must not exists. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8434) Management console should write/read time unit and adjust it

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8434?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8434. -------------------------------- Fix Version/s: 9.2.0.CR1 Resolution: Done > 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 > Assignee: Vladimir Blagojevic > Fix For: 9.2.0.CR1 > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8434) Management console should write/read time unit and adjust it

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-8434?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-8434: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/228/files > 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 > Assignee: Vladimir Blagojevic > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8662) Adjust merge policies for JDG Online Services

by Pedro Zapata (JIRA)

Pedro Zapata created ISPN-8662: ---------------------------------- Summary: Adjust merge policies for JDG Online Services Key: ISPN-8662 URL: https://issues.jboss.org/browse/ISPN-8662 Project: Infinispan Issue Type: Feature Request Components: Cloud Reporter: Pedro Zapata Assignee: Ryan Emerson Fix For: 9.2.0.CR1 Both Shared Memory and Caching Service require custom merge policies. In Caching Service we need to clear out all conflicted entries upon split brain. Shared Memory service might be a little bit more tricky and we might want to use some different strategy (but that needs to be checked out). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8433) Cache counts per node in management console incorrect

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-8433?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-8433: -------------------------------------- Status: Open (was: New) > 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 > Assignee: Vladimir Blagojevic > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8434) Management console should write/read time unit and adjust it

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-8434?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-8434: -------------------------------------- Status: Open (was: New) > 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 > Assignee: Vladimir Blagojevic > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8433) Cache counts per node in management console incorrect

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-8433?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-8433: ----------------------------------------- Assignee: Vladimir Blagojevic > 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 > Assignee: Vladimir Blagojevic > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7739) CacheMgmtInterceptor should collect total writes stat

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7739?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on ISPN-7739: ------------------------------------ [~vblagojevic] I'm not sure I follow, the component is marked as "JMX, reporting and management" which includes infinispan-core. > CacheMgmtInterceptor should collect total writes stat > ----------------------------------------------------- > > Key: ISPN-7739 > URL: https://issues.jboss.org/browse/ISPN-7739 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Affects Versions: 9.0.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2018