June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8848) Revert ISPN-8843 when there's a fix in IntelliJ

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8848?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8848: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Revert ISPN-8843 when there's a fix in IntelliJ > ----------------------------------------------- > > Key: ISPN-8848 > URL: https://issues.jboss.org/browse/ISPN-8848 > Project: Infinispan > Issue Type: Bug > Components: Build > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > Priority: Minor > Fix For: 9.4.0.Final > > > Revert ISPN-8843 when the [IntelliJ bug|https://youtrack.jetbrains.com/issue/IDEA-186904] is fixed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8834) Test persistence of <modules> element in server

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8834?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8834: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Test persistence of <modules> element in server > ----------------------------------------------- > > Key: ISPN-8834 > URL: https://issues.jboss.org/browse/ISPN-8834 > Project: Infinispan > Issue Type: Task > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8801) org.infinispan.tasks classes not in javadoc

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8801?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8801: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > org.infinispan.tasks classes not in javadoc > ------------------------------------------- > > Key: ISPN-8801 > URL: https://issues.jboss.org/browse/ISPN-8801 > Project: Infinispan > Issue Type: Task > Components: Documentation-Servers > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.4.0.Final > > > They're missing from javadocs. They don't appear to be depended from {{javadoc-all}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8799) Limit the default number of shards in the AffinityIndexManager

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8799?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8799: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Limit the default number of shards in the AffinityIndexManager > -------------------------------------------------------------- > > Key: ISPN-8799 > URL: https://issues.jboss.org/browse/ISPN-8799 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.4.0.Final > > > By default this index manager will create as many Lucene indexes as Infinispan segments (256) which will penalize query performance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9029) Add test for exception eviction dropping entries after node leave

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9029?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9029: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Add test for exception eviction dropping entries after node leave > ----------------------------------------------------------------- > > Key: ISPN-9029 > URL: https://issues.jboss.org/browse/ISPN-9029 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: William Burns > Fix For: 9.4.0.Final > > > {{ExceptionEvictionTest}} tests what happens when a node is added and N*limit existing entries are redistributed among N+1 nodes. We also need to test what happens when a node crashes and N*limit entries are redistributed among N-1 nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9028) Write-only segments should be invalidated during the READ_NEW phase

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9028?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9028: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Write-only segments should be invalidated during the READ_NEW phase > ------------------------------------------------------------------- > > Key: ISPN-9028 > URL: https://issues.jboss.org/browse/ISPN-9028 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.4.0.Final > > > When a rebalance removes a segment X from node A, node A keeps updating entries in segment X until the rebalance finishes, and only deletes the entries of segment X after entering the NO_REBALANCE phase. > This is problematic for tests that work with the data container directly, because {{waitForNoRebalance()}} doesn't wait for the removal of stale entries. The test will work without an explicit wait most of the time, so this is a recipe for random test failures (e.g. ISPN-8728). > As described in ISPN-5021, we can prevent any writes to segment X at the start of the READ_NEW_WRITE_ALL phase, send the phase confirmation to the coordinator, and then remove the entries asynchronously. We just need to keep track of the removal task and only install/confirm the NO_REBALANCE phase once all the entries that we don't own have been removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9018) SslTest.testClientAuth random failures

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9018?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9018: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > SslTest.testClientAuth random failures > -------------------------------------- > > Key: ISPN-9018 > URL: https://issues.jboss.org/browse/ISPN-9018 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Labels: testsuite_stability > Fix For: 9.4.0.Final > > > The test fails with a timeout exception. There is probably more, but before ISPN-9017 is fixed gathering logs is too difficult. > {noformat} > 09:34:03,524 DEBUG (testng-Test:[]) [ChannelFactory] Creating new channel pool for 127.0.0.1:12411 > 09:34:09,732 INFO (testng-Test:[]) [RemoteCacheManager] ISPN004021: Infinispan version: null > 09:34:13,823 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.client.hotrod.SslTest.testClientAuth > org.infinispan.client.hotrod.exceptions.TransportException: java.net.SocketTimeoutException: FaultTolerantPingOperation{(default), flags=0} timed out after 3000 ms > at org.infinispan.client.hotrod.impl.Util.rewrap(Util.java:50) ~[classes/:?] > at org.infinispan.client.hotrod.impl.Util.await(Util.java:25) ~[classes/:?] > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.ping(RemoteCacheImpl.java:472) ~[classes/:?] > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.resolveCompatibility(RemoteCacheImpl.java:736) ~[classes/:?] > at org.infinispan.client.hotrod.RemoteCacheManager.createRemoteCache(RemoteCacheManager.java:312) ~[classes/:?] > at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:201) ~[classes/:?] > at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:195) ~[classes/:?] > at org.infinispan.client.hotrod.SslTest.initServerAndClient(SslTest.java:103) ~[test-classes/:?] > at org.infinispan.client.hotrod.SslTest.testClientAuth(SslTest.java:131) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9017) HotRod client thread names should include the test name

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9017?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9017: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > HotRod client thread names should include the test name > ------------------------------------------------------- > > Key: ISPN-9017 > URL: https://issues.jboss.org/browse/ISPN-9017 > Project: Infinispan > Issue Type: Task > Components: Hot Rod, Test Suite - Server > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Radim Vansa > Priority: Minor > Fix For: 9.4.0.Final > > > I wanted to obtain a trace log for a {{SslTest}} failure I'm seeing locally, but when I filter by test name all I get is this: > {noformat} > 09:34:03,524 DEBUG (testng-Test:[]) [ChannelFactory] Creating new channel pool for 127.0.0.1:12411 > 09:34:09,732 INFO (testng-Test:[]) [RemoteCacheManager] ISPN004021: Infinispan version: null > 09:34:13,823 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.client.hotrod.SslTest.testClientAuth > org.infinispan.client.hotrod.exceptions.TransportException: java.net.SocketTimeoutException: FaultTolerantPingOperation{(default), flags=0} timed out after 3000 ms > at org.infinispan.client.hotrod.impl.Util.rewrap(Util.java:50) ~[classes/:?] > at org.infinispan.client.hotrod.impl.Util.await(Util.java:25) ~[classes/:?] > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.ping(RemoteCacheImpl.java:472) ~[classes/:?] > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.resolveCompatibility(RemoteCacheImpl.java:736) ~[classes/:?] > at org.infinispan.client.hotrod.RemoteCacheManager.createRemoteCache(RemoteCacheManager.java:312) ~[classes/:?] > at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:201) ~[classes/:?] > at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:195) ~[classes/:?] > at org.infinispan.client.hotrod.SslTest.initServerAndClient(SslTest.java:103) ~[test-classes/:?] > at org.infinispan.client.hotrod.SslTest.testClientAuth(SslTest.java:131) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8981) Generate Hot Rod parser automatically

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8981?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8981: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Generate Hot Rod parser automatically > ------------------------------------- > > Key: ISPN-8981 > URL: https://issues.jboss.org/browse/ISPN-8981 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 9.2.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.4.0.Final > > > This JIRA has two objectives: > 1. reduce number of allocated objects > 2. improve the parsing on server side to avoid chains of lambda mappings > Manual parsing of Hot Rod protocol, invoking recursive methods that return {{Optional}}s or {{Optional<Optional<...>}}s seems to generate a lot of garbage. A better approach would be a finite state automaton that would read the byte stream and invoke callbacks. > Such automaton can be generated from a high-level grammar as part of the build process. > Along with these changes we can remove the {{Response}} abstraction and write responses directly as {{ByteBuf}}s. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8955) ClusterTopologyManagerImpl should only use non-blocking RPCs

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8955?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8955: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > ClusterTopologyManagerImpl should only use non-blocking RPCs > ------------------------------------------------------------ > > Key: ISPN-8955 > URL: https://issues.jboss.org/browse/ISPN-8955 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.4.0.Final > > > {{ClusterTopologyManagerImpl}} still uses some blocking RPCs, particularly when a node becomes coordinator or after a merge. It should use non-blocking RPCs instead. > It could also use non-blocking RPCs instead of fire-and-forget messages for things like topology updates, which would allow delivering topology updates in the same order on all the nodes instead of having regular nodes make to with missing topology updates (when the coordinator doesn't change). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2018