March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPRK-9) Create Quick Start documentation

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-9?page=com.atlassian.jira.plugin.sy... ] Gustavo Fernandes updated ISPRK-9: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jboss-developer/jboss-jdg-quickstarts/pull/120 > Create Quick Start documentation > -------------------------------- > > Key: ISPRK-9 > URL: https://issues.jboss.org/browse/ISPRK-9 > Project: Infinispan Spark > Issue Type: Task > Reporter: Pedro Zapata > Priority: Minor > Fix For: 0.3 > > > A quick start is required for both the Spark and Hadoop integrations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6395) Unify clustered queries with non clustered queries

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-6395: --------------------------------------- Summary: Unify clustered queries with non clustered queries Key: ISPN-6395 URL: https://issues.jboss.org/browse/ISPN-6395 Project: Infinispan Issue Type: Feature Request Components: Embedded Querying Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes Clustered queries currently have a different API, and they work on top on non-shared indexes. We should detected (or make it explicitly configurable) the fact that the index is not shared and use clustered query internally, but exposing a single Query interface. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6370) Expose DMR operation to find out if a cache is being ignored

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6370?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-6370: ----------------------------------------- [~vblagojevic] I was thinking on this new operation: {code} List<String> getIgnoredEndpoints(cacheName: String) {code} It would be empty if the cache is available for all of them, wdyt? > Expose DMR operation to find out if a cache is being ignored > ------------------------------------------------------------ > > Key: ISPN-6370 > URL: https://issues.jboss.org/browse/ISPN-6370 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6394) Coalesce server group view and Infinispan/JGroups view

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6394?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6394: -------------------------------------- Issue Type: Bug (was: Feature Request) > Coalesce server group view and Infinispan/JGroups view > ------------------------------------------------------ > > Key: ISPN-6394 > URL: https://issues.jboss.org/browse/ISPN-6394 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > Currently the console is using the server-group knowledge (i.e. which host/servers belong to a specific group). While that is definitely the "ideal" situation, we also need to ensure that it corresponds to the "actual" cluster as known to Infinispan/JGroups. This information should be then used to present the user with appropriate warnings if necessary. > For each container %c in each server %s in the server group we need to extract the "members" property: > /host=%h/server=%s/subsystem=datagrid-infinispan/cache-container=%c:read-attribute(name=members) > This returns a list of server names (in the form %h:%s). > This is how we should use the information (in combination with the existing "cluster-availability" property information from the coordinator): > 1. If the server-group list coincides with the container members of all nodes, all is good: the cluster is healthy, all nodes are up and running > 2. If all of the container members contain the SAME subset of the server group, but the missing members are in the STOPPED or STARTING state, everything could be normal: we should depend on the coordinator's "cluster-availability" to tell us if the cluster is unhealthy. > 3. If the container members differ between each other and with the server group view, and all these servers are in RUNNING we have a potential split brain or a cluster which is not formed correctly. > The above deduction should determine not only the label / colour-coding we place in the view header (AVAILABLE, DEGRADED, etc) but also some of the view content: in both the cluster nodes view and the cache nodes view we need to group / sort by membership, so that we clearly show split clusters and stopped nodes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6394) Coalesce server group view and Infinispan/JGroups view

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-6394: ----------------------------------------- Summary: Coalesce server group view and Infinispan/JGroups view Key: ISPN-6394 URL: https://issues.jboss.org/browse/ISPN-6394 Project: Infinispan Issue Type: Feature Request Components: Console Affects Versions: 8.2.0.Final Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Currently the console is using the server-group knowledge (i.e. which host/servers belong to a specific group). While that is definitely the "ideal" situation, we also need to ensure that it corresponds to the "actual" cluster as known to Infinispan/JGroups. This information should be then used to present the user with appropriate warnings if necessary. For each container %c in each server %s in the server group we need to extract the "members" property: /host=%h/server=%s/subsystem=datagrid-infinispan/cache-container=%c:read-attribute(name=members) This returns a list of server names (in the form %h:%s). This is how we should use the information (in combination with the existing "cluster-availability" property information from the coordinator): 1. If the server-group list coincides with the container members of all nodes, all is good: the cluster is healthy, all nodes are up and running 2. If all of the container members contain the SAME subset of the server group, but the missing members are in the STOPPED or STARTING state, everything could be normal: we should depend on the coordinator's "cluster-availability" to tell us if the cluster is unhealthy. 3. If the container members differ between each other and with the server group view, and all these servers are in RUNNING we have a potential split brain or a cluster which is not formed correctly. The above deduction should determine not only the label / colour-coding we place in the view header (AVAILABLE, DEGRADED, etc) but also some of the view content: in both the cluster nodes view and the cache nodes view we need to group / sort by membership, so that we clearly show split clusters and stopped nodes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6370) Expose DMR operation to find out if a cache is being ignored

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6370?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-6370: ------------------------------------------- [~gustavonalle] Any updates on this one? It would be great to have it by Monday so I can squeeze it in for the next release! > Expose DMR operation to find out if a cache is being ignored > ------------------------------------------------------------ > > Key: ISPN-6370 > URL: https://issues.jboss.org/browse/ISPN-6370 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 8.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6393) Add ability to hide configuration properties

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-6393: ----------------------------------------- Summary: Add ability to hide configuration properties Key: ISPN-6393 URL: https://issues.jboss.org/browse/ISPN-6393 Project: Infinispan Issue Type: Feature Request Components: Console Affects Versions: 8.2.0.Final Reporter: Vladimir Blagojevic We should add ability to hide certain configuration fields if needed. We could hide these fields directly from javascript or preferably from some specific configuration file. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6393) Add ability to hide configuration properties

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6393?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-6393: ----------------------------------------- Assignee: Vladimir Blagojevic > Add ability to hide configuration properties > -------------------------------------------- > > Key: ISPN-6393 > URL: https://issues.jboss.org/browse/ISPN-6393 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > We should add ability to hide certain configuration fields if needed. We could hide these fields directly from javascript or preferably from some specific configuration file. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6230) Task history tab does not show tasks unless Refresh button is pressed as well

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6230?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6230: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/73 > Task history tab does not show tasks unless Refresh button is pressed as well > ----------------------------------------------------------------------------- > > Key: ISPN-6230 > URL: https://issues.jboss.org/browse/ISPN-6230 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Reporter: Martin Gencur > Assignee: Vladimir Blagojevic > Priority: Minor > > This is rather a small usability issue: > When I run a task and then click "Task history", the tab doesn't show any tasks. I have to click "Refresh" and only then the tasks are displayed. It might be better to call refresh when "Task history" tab is clicked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6230) Task history tab does not show tasks unless Refresh button is pressed as well

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6230?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6230: -------------------------------------- Status: Open (was: New) > Task history tab does not show tasks unless Refresh button is pressed as well > ----------------------------------------------------------------------------- > > Key: ISPN-6230 > URL: https://issues.jboss.org/browse/ISPN-6230 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Reporter: Martin Gencur > Assignee: Vladimir Blagojevic > Priority: Minor > > This is rather a small usability issue: > When I run a task and then click "Task history", the tab doesn't show any tasks. I have to click "Refresh" and only then the tasks are displayed. It might be better to call refresh when "Task history" tab is clicked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2016