April 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9021) Remote query: add option to disable default/legacy indexing per schema file

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9021?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9021: ---------------------------------- Fix Version/s: 9.3.0.Beta1 (was: 9.3.0.Alpha1) > Remote query: add option to disable default/legacy indexing per schema file > --------------------------------------------------------------------------- > > Key: ISPN-9021 > URL: https://issues.jboss.org/browse/ISPN-9021 > Project: Infinispan > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.3.0.Beta1, 9.3.0.Final > > > All types that are not annotated are currently fully indexed for backward compat with first version of remote query (which did not have protobuf annotations to control indexing). > This behaviour is very inefficient and confusing for users that do not intend to use indexing (non-indexed query works anyway). > Given the history of this behaviour we cannot remove it until next major version. Until then we can offer the choice of disabling it per each schema file via a boolean protobuf file-level option named 'enable_legacy_indexing', which when absent is considered to default to true. Setting it to false will disable indexing of types that do not have indexing annotations. > Whenever an entry is indexed using default indexing a warning will be logged in order to motivate people to switch to using proper annotations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9018?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9018: ---------------------------------- Fix Version/s: 9.3.0.Beta1 (was: 9.3.0.Alpha1) > 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.3.0.Beta1 > > > 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)

7 years, 8 months

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9017?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9017: ---------------------------------- Fix Version/s: 9.3.0.Beta1 (was: 9.3.0.Alpha1) > 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.3.0.Beta1 > > > 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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9016) Component metadata serialization format changes depending on compiler

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9016?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9016: ---------------------------------- Fix Version/s: 9.3.0.Beta1 (was: 9.3.0.Alpha1) > Component metadata serialization format changes depending on compiler > --------------------------------------------------------------------- > > Key: ISPN-9016 > URL: https://issues.jboss.org/browse/ISPN-9016 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Beta1 > > > The field and method metadata classes have a {{serialVersionUUID}}, but {{ComponentMetadata}} itself doesn't have it, so it can change at any time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9089) Conflict Resolution phase should be non-blocking and restart on node failures

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9089?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9089: ---------------------------------- Fix Version/s: 9.3.0.Beta1 (was: 9.3.0.Alpha1) > Conflict Resolution phase should be non-blocking and restart on node failures > ----------------------------------------------------------------------------- > > Key: ISPN-9089 > URL: https://issues.jboss.org/browse/ISPN-9089 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Beta1 > > > Currently if a node crashes during the conflict resolution phase, all topology updates and rebalancing is blocked until CR times out. As the CR timeout is the state transfer timeout, this means the cluster is in limbo for 4 minutes by default. This blocking behaviour occurs because currently the entire CR phase is executed in the merge thread, however it should occur asynchronously in a similar manner to a cache rebalance with CR restarting in the event of nodes leaving. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9086) Improve logging of topology updates

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9086?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9086: ---------------------------------- Fix Version/s: 9.3.0.Beta1 (was: 9.3.0.Alpha1) > Improve logging of topology updates > ----------------------------------- > > Key: ISPN-9086 > URL: https://issues.jboss.org/browse/ISPN-9086 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.Beta1 > > > Rebalance confirmations are logged with the event logger, but topology updates aren't. It should be the other way around, because the number of confirmations grows with the cluster size, and the number of topology updates only depends on the number of caches and joiners/leavers. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9079) Cache operations during Conflict Resolution phase should force CR on that key

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9079?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9079: ---------------------------------- Fix Version/s: 9.3.0.Beta1 (was: 9.3.0.Alpha1) > Cache operations during Conflict Resolution phase should force CR on that key > ----------------------------------------------------------------------------- > > Key: ISPN-9079 > URL: https://issues.jboss.org/browse/ISPN-9079 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Beta1 > > > During a partition merge conflict resolution can take a long time when there are many entries, therefore if a user initiates an operation on a key during this phase, it should force CR to occur on the key before executing the operation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8936) Parameterized branding

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8936?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8936: ---------------------------------- Sprint: Sprint 9.3.0.Beta1 (was: Sprint 9.3.0.Alpha1) > Parameterized branding > ---------------------- > > Key: ISPN-8936 > URL: https://issues.jboss.org/browse/ISPN-8936 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Alpha1 > > > The Infinispan name is included in a number of artifacts: > * javadocs > * documentation > * CLI > * Server startup banner > * Console > * zip distributions > These should be parameterizable for productization -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8997) Publish maven snapshot artifacts on stable master builds

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8997?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8997: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1, Sprint 9.3.0.Beta1 (was: Sprint 9.3.0.Alpha1) > Publish maven snapshot artifacts on stable master builds > -------------------------------------------------------- > > Key: ISPN-8997 > URL: https://issues.jboss.org/browse/ISPN-8997 > Project: Infinispan > Issue Type: Bug > Components: Build, CI > Reporter: Tristan Tarrant > Assignee: Sebastian Łaskawiec > > Successful builds of the master branch should publish snapshot artifacts to Maven -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9000) Send e-mails for nightly builds to Infinispan CI mailing list

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9000?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9000: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1, Sprint 9.3.0.Beta1 (was: Sprint 9.3.0.Alpha1) > Send e-mails for nightly builds to Infinispan CI mailing list > ------------------------------------------------------------- > > Key: ISPN-9000 > URL: https://issues.jboss.org/browse/ISPN-9000 > Project: Infinispan > Issue Type: Bug > Components: CI > Reporter: Tristan Tarrant > Assignee: Vittorio Rigamonti > > The branch builds (master, stable, etc) should send results to the infinispan ci mailing list -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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