April 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9066) Successfully configured Slave node with no server configured is not shown in the list of hosts

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-9066?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9066: -------------------------------------- Security: (was: Red Hat Internal) > Successfully configured Slave node with no server configured is not shown in the list of hosts > ----------------------------------------------------------------------------------------------- > > Key: ISPN-9066 > URL: https://issues.jboss.org/browse/ISPN-9066 > Project: Infinispan > Issue Type: Bug > Components: Console > Environment: * Mac OS X > * Out of the box Infinispan setup with no customization of domain and host XML files > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Attachments: Screen Shot 2018-04-10 at 4.06.46 PM.png > > > Considering two host setup (master and slave), where the master host is running the domain controller and host controller whereas slave host is only running the slave controller. If the slave's host.xml does not have any servers initially configured, despite successful registration with the domain controller running on master, the slave host does appear for the drop-down of the *Add Node* feature on the page *Clutsers → Cluster*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9064) SiteManualSwitchTest.testManualClusterSwitch randomly fails

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9064?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-9064: ---------------------------------------- Last known failure: https://ci.infinispan.org/job/Infinispan/job/master/558/testReport/junit/... > SiteManualSwitchTest.testManualClusterSwitch randomly fails > ----------------------------------------------------------- > > Key: ISPN-9064 > URL: https://issues.jboss.org/browse/ISPN-9064 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Reporter: Galder Zamarreño > Labels: testsuite_stability > Fix For: 9.3.0.Beta1, 9.3.0.Final > > > {code} > java.lang.AssertionError: expected:<1> but was:<0> > at org.infinispan.client.hotrod.xsite.AbstractHotRodSiteFailoverTest.assertSiteHit(AbstractHotRodSiteFailoverTest.java:146) > at org.infinispan.client.hotrod.xsite.SiteManualSwitchTest.assertSingleSiteHit(SiteManualSwitchTest.java:47) > at org.infinispan.client.hotrod.xsite.SiteManualSwitchTest.testManualClusterSwitch(SiteManualSwitchTest.java:37) > 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) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9064) SiteManualSwitchTest.testManualClusterSwitch randomly fails

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9064?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9064: ----------------------------------- Status: Open (was: New) > SiteManualSwitchTest.testManualClusterSwitch randomly fails > ----------------------------------------------------------- > > Key: ISPN-9064 > URL: https://issues.jboss.org/browse/ISPN-9064 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Reporter: Galder Zamarreño > Labels: testsuite_stability > Fix For: 9.3.0.Beta1, 9.3.0.Final > > > {code} > java.lang.AssertionError: expected:<1> but was:<0> > at org.infinispan.client.hotrod.xsite.AbstractHotRodSiteFailoverTest.assertSiteHit(AbstractHotRodSiteFailoverTest.java:146) > at org.infinispan.client.hotrod.xsite.SiteManualSwitchTest.assertSingleSiteHit(SiteManualSwitchTest.java:47) > at org.infinispan.client.hotrod.xsite.SiteManualSwitchTest.testManualClusterSwitch(SiteManualSwitchTest.java:37) > 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) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9064) SiteManualSwitchTest.testManualClusterSwitch randomly fails

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9064?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9064: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5913 > SiteManualSwitchTest.testManualClusterSwitch randomly fails > ----------------------------------------------------------- > > Key: ISPN-9064 > URL: https://issues.jboss.org/browse/ISPN-9064 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Reporter: Galder Zamarreño > Labels: testsuite_stability > Fix For: 9.3.0.Beta1, 9.3.0.Final > > > {code} > java.lang.AssertionError: expected:<1> but was:<0> > at org.infinispan.client.hotrod.xsite.AbstractHotRodSiteFailoverTest.assertSiteHit(AbstractHotRodSiteFailoverTest.java:146) > at org.infinispan.client.hotrod.xsite.SiteManualSwitchTest.assertSingleSiteHit(SiteManualSwitchTest.java:47) > at org.infinispan.client.hotrod.xsite.SiteManualSwitchTest.testManualClusterSwitch(SiteManualSwitchTest.java:37) > 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) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9065) JGroupsTransport should only send messages to nodes in the cluster view

by Pedro Zapata (JIRA)

Pedro Zapata created ISPN-9065: ---------------------------------- Summary: JGroupsTransport should only send messages to nodes in the cluster view Key: ISPN-9065 URL: https://issues.jboss.org/browse/ISPN-9065 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.2.1.Final Reporter: Pedro Zapata Assignee: Dan Berindei Fix For: 9.2.2.Final, 9.3.0.Alpha1 {{JGroupsTransport}} only waits for responses from nodes in the JGroups cluster view, but it still sends messages to all the nodes specified as a target. The idea was to optimize the common case by avoiding a {{HashSet.contains()}} call. However, when a node is not in the view, messages to it still pass through the entire JGroups stack, and UNICAST3 keeps those messages in a send table for a long time ({{UNICAST3.conn_expiry_timeout}}, changed with ISPN-9038 from {{0}} (unlimited) to 2 minutes (JGroups default)). Having a potentially unlimited number of messages of non-members, each with its own send table, makes it much harder to estimate memory usage. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9064) SiteManualSwitchTest.testManualClusterSwitch randomly fails

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-9064: -------------------------------------- Summary: SiteManualSwitchTest.testManualClusterSwitch randomly fails Key: ISPN-9064 URL: https://issues.jboss.org/browse/ISPN-9064 Project: Infinispan Issue Type: Bug Components: Remote Protocols Reporter: Galder Zamarreño Fix For: 9.3.0.Beta1, 9.3.0.Final {code} java.lang.AssertionError: expected:<1> but was:<0> at org.infinispan.client.hotrod.xsite.AbstractHotRodSiteFailoverTest.assertSiteHit(AbstractHotRodSiteFailoverTest.java:146) at org.infinispan.client.hotrod.xsite.SiteManualSwitchTest.assertSingleSiteHit(SiteManualSwitchTest.java:47) at org.infinispan.client.hotrod.xsite.SiteManualSwitchTest.testManualClusterSwitch(SiteManualSwitchTest.java:37) 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) {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9063) Average stats should be calculated in Nanoseconds but exposed in Milliseconds

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9063?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9063: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5911 > Average stats should be calculated in Nanoseconds but exposed in Milliseconds > ----------------------------------------------------------------------------- > > Key: ISPN-9063 > URL: https://issues.jboss.org/browse/ISPN-9063 > Project: Infinispan > Issue Type: Bug > Components: Console, JMX, reporting and management > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Alpha1 > > > ISPN-7768 changed the precision of the exposed average-<read|write>time stats from Milliseconds to Nanoseconds. This causes backwards compatibility issues with previous versions of Infinispan and JDG. Therefore we need to ensure that these stats are exposed to the user in Milliseconds, however they should still be calculated in Nanoseconds internally to improve accuracy and avoid rounding errors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9063) Average stats should be calculated in Nanoseconds but exposed in Milliseconds

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9063?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9063: ------------------------------- Status: Open (was: New) > Average stats should be calculated in Nanoseconds but exposed in Milliseconds > ----------------------------------------------------------------------------- > > Key: ISPN-9063 > URL: https://issues.jboss.org/browse/ISPN-9063 > Project: Infinispan > Issue Type: Bug > Components: Console, JMX, reporting and management > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Alpha1 > > > ISPN-7768 changed the precision of the exposed average-<read|write>time stats from Milliseconds to Nanoseconds. This causes backwards compatibility issues with previous versions of Infinispan and JDG. Therefore we need to ensure that these stats are exposed to the user in Milliseconds, however they should still be calculated in Nanoseconds internally to improve accuracy and avoid rounding errors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9062) JGroupsTransport should only send messages to nodes in the cluster view

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9062?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9062: ------------------------------- Status: Open (was: New) > JGroupsTransport should only send messages to nodes in the cluster view > ----------------------------------------------------------------------- > > Key: ISPN-9062 > URL: https://issues.jboss.org/browse/ISPN-9062 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.2.Final, 9.3.0.Alpha1 > > > {{JGroupsTransport}} only waits for responses from nodes in the JGroups cluster view, but it still sends messages to all the nodes specified as a target. The idea was to optimize the common case by avoiding a {{HashSet.contains()}} call. > However, when a node is not in the view, messages to it still pass through the entire JGroups stack, and UNICAST3 keeps those messages in a send table for a long time ({{UNICAST3.conn_expiry_timeout}}, changed with ISPN-9038 from {{0}} (unlimited) to 2 minutes (JGroups default)). Having a potentially unlimited number of messages of non-members, each with its own send table, makes it much harder to estimate memory usage. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9063) Average stats should be calculated in Nanoseconds but exposed in Milliseconds

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-9063: ---------------------------------- Summary: Average stats should be calculated in Nanoseconds but exposed in Milliseconds Key: ISPN-9063 URL: https://issues.jboss.org/browse/ISPN-9063 Project: Infinispan Issue Type: Bug Components: Console, JMX, reporting and management Affects Versions: 9.2.1.Final Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 9.3.0.Alpha1 ISPN-7768 changed the precision of the exposed average-<read|write>time stats from Milliseconds to Nanoseconds. This causes backwards compatibility issues with previous versions of Infinispan and JDG. Therefore we need to ensure that these stats are exposed to the user in Milliseconds, however they should still be calculated in Nanoseconds internally to improve accuracy and avoid rounding errors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 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 April 2018