May 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6587) Eviction type does not chage after reconfiguring in console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6587?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6587: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha3 Resolution: Done > Eviction type does not chage after reconfiguring in console > ----------------------------------------------------------- > > Key: ISPN-6587 > URL: https://issues.jboss.org/browse/ISPN-6587 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.0.Alpha3 > > > container -> cache -> configuration -> eviction -> eviction type > "Type" was empty before. > After changing it to COUNT or MEMORY and afterwards open the configuration page again to check if it was changed the "Type" remained empty. > The JMX value was also not changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6579) Migrate near cache demo to a separate repo

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6579?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6579: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Migrate near cache demo to a separate repo > ------------------------------------------ > > Key: ISPN-6579 > URL: https://issues.jboss.org/browse/ISPN-6579 > Project: Infinispan > Issue Type: Task > Components: Demos and Tutorials > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha2, 9.0.0.Final > > > And also remove the jnp-[client|server] dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6589) ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6589?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6589: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4305, https://github.com/infinispan/infinispan/pull/4306 (was: https://github.com/infinispan/infinispan/pull/4305) > ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed > ----------------------------------------------------------------------------- > > Key: ISPN-6589 > URL: https://issues.jboss.org/browse/ISPN-6589 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 8.0.0.Final, 9.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > Nested indexed fields may sometimes be reported as unindexed even if the metadata says otherwise. This may cause a query to be run fully or partially unindexed leading to perf issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-22) InfinispanRDD is not fault tolerant

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPRK-22: ------------------------------------ Summary: InfinispanRDD is not fault tolerant Key: ISPRK-22 URL: https://issues.jboss.org/browse/ISPRK-22 Project: Infinispan Spark Issue Type: Bug Components: RDD Affects Versions: 0.3 Reporter: Vojtech Juranek When primary ISPN server fails during processing InfinispanRDD, Spark is not able to overcome this failure. This is caused by re-creating {{RemoteCachManager}} with pre-configured ISPN server address (for read [here|https://github.com/infinispan/infinispan-spark/blob/master/src/main/...], for writes [here|https://github.com/infinispan/infinispan-spark/blob/master/src/main/...]), so when this server fails during RDD processing and Spark calls some function, which under the hood creates {{RemoteCacheManager}}, it will fail with connection refused exception. [Here|https://github.com/vjuranek/infinispan-spark/commit/9aef6b7269feadb9...] are some basic tests (requires some more work, but should be fine for reproducing the issue) and example of exception thrown by HR client: {noformat} org.infinispan.client.hotrod.exceptions.TransportException:: Could not fetch transport at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.borrowTransportFromPool(TcpTransportFactory.java:395) at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.getTransport(TcpTransportFactory.java:241) at org.infinispan.client.hotrod.impl.operations.FaultTolerantPingOperation.getTransport(FaultTolerantPingOperation.java:26) at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:53) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.ping(RemoteCacheImpl.java:490) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.resolveCompatibility(RemoteCacheImpl.java:551) at org.infinispan.client.hotrod.RemoteCacheManager.createRemoteCache(RemoteCacheManager.java:341) at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:222) at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:217) at org.infinispan.spark.rdd.InfinispanRDD$$anonfun$1.apply(InfinispanRDD.scala:52) at org.infinispan.spark.rdd.InfinispanRDD$$anonfun$1.apply(InfinispanRDD.scala:52) at scala.Option.map(Option.scala:146) at org.infinispan.spark.rdd.InfinispanRDD.compute(InfinispanRDD.scala:52) at org.infinispan.spark.rdd.InfinispanRDD.compute(InfinispanRDD.scala:66) at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:306) at org.apache.spark.rdd.RDD.iterator(RDD.scala:270) at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:66) at org.apache.spark.scheduler.Task.run(Task.scala:89) at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:213) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.infinispan.client.hotrod.exceptions.TransportException:: Could not connect to server: /127.0.0.1:11222 at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:78) at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:35) at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:16) at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220) at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.borrowTransportFromPool(TcpTransportFactory.java:390) ... 21 more Caused by: java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:111) at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:68) ... 25 more {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6577) Indexing properties should be stored in a distinct subresource to ease configuration inheritance

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6577?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6577: ---------------------------------- Summary: Indexing properties should be stored in a distinct subresource to ease configuration inheritance (was: Cache configuration ignored when configured with "configuration" element) > Indexing properties should be stored in a distinct subresource to ease configuration inheritance > ------------------------------------------------------------------------------------------------ > > Key: ISPN-6577 > URL: https://issues.jboss.org/browse/ISPN-6577 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.1.Final, 9.0.0.Alpha1 > Reporter: Gustavo Fernandes > Assignee: Tristan Tarrant > Priority: Critical > > Given the following config: > {code:xml} > <replicated-cache-configuration name="indexed-cache" mode="SYNC" start="EAGER" remote-timeout="20000"/> > <replicated-cache name="booksCache" configuration="indexed-cache"> > <indexing index="LOCAL"> > <property name="default.metadata_cachename">indexMetadataBooksCache</property> > <property name="default.data_cachename">indexDataBooksCache</property> > <property name="default.locking_cachename">indexLockingBooksCache</property> > <property name="default.directory_provider">infinispan</property> > <property name="default.indexmanager">org.infinispan.query.indexmanager.InfinispanIndexManager</property> > <property name="lucene_version">LUCENE_CURRENT</property> > </indexing> > </replicated-cache> > {code} > The booksCache starts in non-indexed mode, even if it explicitly configure the indexing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6589) ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6589?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6589: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/4305 > ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed > ----------------------------------------------------------------------------- > > Key: ISPN-6589 > URL: https://issues.jboss.org/browse/ISPN-6589 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 8.0.0.Final, 9.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > Nested indexed fields may sometimes be reported as unindexed even if the metadata says otherwise. This may cause a query to be run fully or partially unindexed leading to perf issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6589) ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6589?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6589: -------------------------------- Affects Version/s: 8.0.0.Final > ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed > ----------------------------------------------------------------------------- > > Key: ISPN-6589 > URL: https://issues.jboss.org/browse/ISPN-6589 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 8.0.0.Final, 9.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > Nested indexed fields may sometimes be reported as unindexed even if the metadata says otherwise. This may cause a query to be run fully or partially unindexed leading to perf issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6589) ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6589?page=com.atlassian.jira.plugin.... ] Work on ISPN-6589 started by Adrian Nistor. ------------------------------------------- > ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed > ----------------------------------------------------------------------------- > > Key: ISPN-6589 > URL: https://issues.jboss.org/browse/ISPN-6589 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 8.0.0.Final, 9.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > Nested indexed fields may sometimes be reported as unindexed even if the metadata says otherwise. This may cause a query to be run fully or partially unindexed leading to perf issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6589) ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6589: ----------------------------------- Summary: ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed Key: ISPN-6589 URL: https://issues.jboss.org/browse/ISPN-6589 Project: Infinispan Issue Type: Bug Components: Remote Querying Affects Versions: 9.0.0.Alpha1 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 9.0.0.Alpha2 Nested indexed fields may sometimes be reported as unindexed even if the metadata says otherwise. This may cause a query to be run fully or partially unindexed leading to perf issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6589) ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6589?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6589: -------------------------------- Status: Open (was: New) > ProtobufIndexedFieldProvider may mistakenly report nested fields as unindexed > ----------------------------------------------------------------------------- > > Key: ISPN-6589 > URL: https://issues.jboss.org/browse/ISPN-6589 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 8.0.0.Final, 9.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > Nested indexed fields may sometimes be reported as unindexed even if the metadata says otherwise. This may cause a query to be run fully or partially unindexed leading to perf issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2016