April 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9058) Auto-start feature/flag for nodes added from Management Console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-9058?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9058: -------------------------------------- Security: (was: Red Hat Internal) > Auto-start feature/flag for nodes added from Management Console > --------------------------------------------------------------- > > Key: ISPN-9058 > URL: https://issues.jboss.org/browse/ISPN-9058 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > > Currently when a new JDG node is added via the management console on any of the configured hosts and when the entire JDG cluster including the domain controller is reboot for any reason, the nodes added via the management console would not come up by default. This is because the host.xml got updated with the server entry but the *auto-start* attribute on the *<server>* was not set to *true*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9058) Auto-start feature/flag for nodes added from Management Console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-9058?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9058: -------------------------------------- Description: Currently when a new Infinispan node is added via the management console on any of the configured hosts and when the entire JDG cluster including the domain controller is reboot for any reason, the nodes added via the management console would not come up by default. This is because the host.xml got updated with the server entry but the *auto-start* attribute on the *<server>* was not set to *true*. (was: Currently when a new JDG node is added via the management console on any of the configured hosts and when the entire JDG cluster including the domain controller is reboot for any reason, the nodes added via the management console would not come up by default. This is because the host.xml got updated with the server entry but the *auto-start* attribute on the *<server>* was not set to *true*.) > Auto-start feature/flag for nodes added from Management Console > --------------------------------------------------------------- > > Key: ISPN-9058 > URL: https://issues.jboss.org/browse/ISPN-9058 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > > Currently when a new Infinispan node is added via the management console on any of the configured hosts and when the entire JDG cluster including the domain controller is reboot for any reason, the nodes added via the management console would not come up by default. This is because the host.xml got updated with the server entry but the *auto-start* attribute on the *<server>* was not set to *true*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9058) Auto-start feature/flag for nodes added from Management Console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-9058?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9058: -------------------------------------- Description: Currently when a new Infinispan node is added via the management console on any of the configured hosts and when the entire Infnispan cluster including the domain controller is reboot for any reason, the nodes added via the management console would not come up by default. This is because the host.xml got updated with the server entry but the *auto-start* attribute on the *<server>* was not set to *true*. (was: Currently when a new Infinispan node is added via the management console on any of the configured hosts and when the entire JDG cluster including the domain controller is reboot for any reason, the nodes added via the management console would not come up by default. This is because the host.xml got updated with the server entry but the *auto-start* attribute on the *<server>* was not set to *true*.) > Auto-start feature/flag for nodes added from Management Console > --------------------------------------------------------------- > > Key: ISPN-9058 > URL: https://issues.jboss.org/browse/ISPN-9058 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > > Currently when a new Infinispan node is added via the management console on any of the configured hosts and when the entire Infnispan cluster including the domain controller is reboot for any reason, the nodes added via the management console would not come up by default. This is because the host.xml got updated with the server entry but the *auto-start* attribute on the *<server>* was not set to *true*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9057) JGroupsTransport.invokeCommand should return a CompletionStage

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9057?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9057: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5910 > JGroupsTransport.invokeCommand should return a CompletionStage > -------------------------------------------------------------- > > Key: ISPN-9057 > URL: https://issues.jboss.org/browse/ISPN-9057 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Alpha1 > > > I changed the {{Transport}} interface to return {{CompletionStage}}, but I forgot about the implementations in {{JGroupsTransport}}, and that means an extra synthetic method. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9008) RpcManager.invokeCommandOnAll ignores cache member that are not in the cluster view

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9008?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9008: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5909 > RpcManager.invokeCommandOnAll ignores cache member that are not in the cluster view > ----------------------------------------------------------------------------------- > > Key: ISPN-9008 > URL: https://issues.jboss.org/browse/ISPN-9008 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.Alpha1 > > > {{RpcManager.invokeCommandOnAll}} broadcasts the command to all the members of the JGroups cluster view, and the {{ResponseCollector}} is not notified if any members of the cache are not in the cluster view. > This is a problem in replicated caches with partition handling enabled, because it means a write can succeed in a minority partition in the time interval between {{JGroupsTransport}} seeing the minority cluster view and {{DistributionManagerImpl}} installing the {{DEGRADED_MODE}} cache topology. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9057) JGroupsTransport.invokeCommand should return a CompletionStage

by Dan Berindei (JIRA)

Dan Berindei created ISPN-9057: ---------------------------------- Summary: JGroupsTransport.invokeCommand should return a CompletionStage Key: ISPN-9057 URL: https://issues.jboss.org/browse/ISPN-9057 Project: Infinispan Issue Type: Task Components: Core Affects Versions: 9.2.1.Final Reporter: Dan Berindei Assignee: Dan Berindei Priority: Minor Fix For: 9.3.0.Alpha1 I changed the {{Transport}} interface to return {{CompletionStage}}, but I forgot about the implementations in {{JGroupsTransport}}, and that means an extra synthetic method. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9057) JGroupsTransport.invokeCommand should return a CompletionStage

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9057?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9057: ------------------------------- Status: Open (was: New) > JGroupsTransport.invokeCommand should return a CompletionStage > -------------------------------------------------------------- > > Key: ISPN-9057 > URL: https://issues.jboss.org/browse/ISPN-9057 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Alpha1 > > > I changed the {{Transport}} interface to return {{CompletionStage}}, but I forgot about the implementations in {{JGroupsTransport}}, and that means an extra synthetic method. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9055) Gui demo fails with "Could not find or load main class org.infinispan.Version"

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9055?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-9055: --------------------------------------- You should use ./bin/runGuiDemo.sh because the classpath needs some dependencies. > Gui demo fails with "Could not find or load main class org.infinispan.Version" > ------------------------------------------------------------------------------ > > Key: ISPN-9055 > URL: https://issues.jboss.org/browse/ISPN-9055 > Project: Infinispan > Issue Type: Bug > Components: Demos and Tutorials > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > > When trying to run the demo with `java -jar infinispan-gui-demo-9.3.0-SNAPSHOT.jar -Djgroups.bind_addr=127.0.0.1 -Djava.net.preferIPv4Stack=true` the following error occurs: > {code} > Error: Could not find or load main class org.infinispan.Version > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9056) Cache metrics per node not displayed when one of nodes is stopped

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-9056?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9056: -------------------------------------- Steps to Reproduce: # Start the Infispan cluster in domain mode locally with out-of-the-box configuration files and with command $JDG_HOME/bin/domain.sh # Navigate to the URL http://127.0.0.1:9990/console/index.html#/server-groups/cluster/master/se... and then choose *Stop* in the *Actions* droop-down on the right # Now try to navigate to the URL http://127.0.0.1:9990/console/index.html#/containers/clustered/clustered/... was: # Install JDG 7.1.0 and patch it with jboss-datagrid-7.1.2-server-patch.zip # Start the JDG cluster in domain mode locally with out-of-the-box configuration files and with command $JDG_HOME/bin/domain.sh # Navigate to the URL http://127.0.0.1:9990/console/index.html#/server-groups/cluster/master/se... and then choose *Stop* in the *Actions* droop-down on the right # Now try to navigate to the URL http://127.0.0.1:9990/console/index.html#/containers/clustered/clustered/... > Cache metrics per node not displayed when one of nodes is stopped > ----------------------------------------------------------------- > > Key: ISPN-9056 > URL: https://issues.jboss.org/browse/ISPN-9056 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.2.1.Final, 9.1.7.Final > Environment: * Mac OS X > * Out of the box JDG setup with no customization of domain and host XML files > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > > When trying to get the stats of any cache (default, repl, memcachedCache) via the Management Console per any available node particularly when one of the Infnispan nodes in deliberately shut down (system calls it DEGRADED mode),the UI throws an error saying the stats couldn't be retrieved from the node shut down. > For example, with the out of the box configuration host.xml starts two server(server-one and server-two). When the server-two is intentionally shut down and when metrics for the distributed cache "default" is looked up for all the available nodes the following error is thrown: > WFLYCTL0030: No resource definition is registered for address [ ("host" => "master"), ("server" => "server-two"), ("subsystem" => "datagrid-infinispan"), ("cache-container" => "clustered"), ("distributed-cache" => "default") ] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9056) Cache metrics per node not displayed when one of nodes is stopped

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-9056?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9056: -------------------------------------- Description: When trying to get the stats of any cache (default, repl, memcachedCache) via the Management Console per any available node particularly when one of the Infnispan nodes in deliberately shut down (system calls it DEGRADED mode),the UI throws an error saying the stats couldn't be retrieved from the node shut down. For example, with the out of the box configuration host.xml starts two server(server-one and server-two). When the server-two is intentionally shut down and when metrics for the distributed cache "default" is looked up for all the available nodes the following error is thrown: WFLYCTL0030: No resource definition is registered for address [ ("host" => "master"), ("server" => "server-two"), ("subsystem" => "datagrid-infinispan"), ("cache-container" => "clustered"), ("distributed-cache" => "default") ] was: When trying to get the stats of any cache (default, repl, memcachedCache) via the Management Console per any available node particularly when one of the JDG nodes in deliberately shut down (system calls it DEGRADED mode),the UI throws an error saying the stats couldn't be retrieved from the node shut down. For example, with the out of the box configuration host.xml starts two server(server-one and server-two). When the server-two is intentionally shut down and when metrics for the distributed cache "default" is looked up for all the available nodes the following error is thrown: WFLYCTL0030: No resource definition is registered for address [ ("host" => "master"), ("server" => "server-two"), ("subsystem" => "datagrid-infinispan"), ("cache-container" => "clustered"), ("distributed-cache" => "default") ] > Cache metrics per node not displayed when one of nodes is stopped > ----------------------------------------------------------------- > > Key: ISPN-9056 > URL: https://issues.jboss.org/browse/ISPN-9056 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.2.1.Final, 9.1.7.Final > Environment: * Mac OS X > * Out of the box JDG setup with no customization of domain and host XML files > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > > When trying to get the stats of any cache (default, repl, memcachedCache) via the Management Console per any available node particularly when one of the Infnispan nodes in deliberately shut down (system calls it DEGRADED mode),the UI throws an error saying the stats couldn't be retrieved from the node shut down. > For example, with the out of the box configuration host.xml starts two server(server-one and server-two). When the server-two is intentionally shut down and when metrics for the distributed cache "default" is looked up for all the available nodes the following error is thrown: > WFLYCTL0030: No resource definition is registered for address [ ("host" => "master"), ("server" => "server-two"), ("subsystem" => "datagrid-infinispan"), ("cache-container" => "clustered"), ("distributed-cache" => "default") ] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2018