September 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4670) Profile and fine-tune the implementation of indexless query

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4670?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4670: ----------------------------------------------- Radim Vansa <rvansa(a)redhat.com> changed the Status of [bug 1140840|https://bugzilla.redhat.com/show_bug.cgi?id=1140840] from ON_QA to VERIFIED > Profile and fine-tune the implementation of indexless query > ----------------------------------------------------------- > > Key: ISPN-4670 > URL: https://issues.jboss.org/browse/ISPN-4670 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Affects Versions: 7.0.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4731) Update classpath to ensure Weld loads Guava instead of Google Collections

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4731?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4731: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1142230 > Update classpath to ensure Weld loads Guava instead of Google Collections > ------------------------------------------------------------------------- > > Key: ISPN-4731 > URL: https://issues.jboss.org/browse/ISPN-4731 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration, Integration > Affects Versions: 7.0.0.Beta2 > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Labels: maven > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4731) Update classpath to ensure Weld loads Guava instead of Google Collections

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-4731: ----------------------------------------- Summary: Update classpath to ensure Weld loads Guava instead of Google Collections Key: ISPN-4731 URL: https://issues.jboss.org/browse/ISPN-4731 Project: Infinispan Issue Type: Bug Components: CDI Integration, Integration Affects Versions: 7.0.0.Beta2 Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4611) Explore ability to use Put-Async in some operations on the Lucene Directory

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4611?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4611: ---------------------------------- Assignee: Gustavo Fernandes (was: Sanne Grinovero) > Explore ability to use Put-Async in some operations on the Lucene Directory > --------------------------------------------------------------------------- > > Key: ISPN-4611 > URL: https://issues.jboss.org/browse/ISPN-4611 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Attachments: 0001-ISPN-4611-Update-write-operations-on-the-list-of-def.patch > > > I just noticed that if I change all put operations in FileListOperations to be putAsync, the stress tests against index corruption and parallel queries run flawlessly. > It's possible that these particular operation might not need the synchronous flush, but we need to verify if a committed index change is immediately visible to queries. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4611) Explore ability to use Put-Async in some operations on the Lucene Directory

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4611?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4611: ---------------------------------- Attachment: 0001-ISPN-4611-Update-write-operations-on-the-list-of-def.patch This is the draft of the changes I'd like to explore. Needs to: - adjust existing tests to deal with it - make sure stress tests are fine (index isn't considered corrupted) - make sure that results will always contain last flushed changes (needs a new test) > Explore ability to use Put-Async in some operations on the Lucene Directory > --------------------------------------------------------------------------- > > Key: ISPN-4611 > URL: https://issues.jboss.org/browse/ISPN-4611 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Attachments: 0001-ISPN-4611-Update-write-operations-on-the-list-of-def.patch > > > I just noticed that if I change all put operations in FileListOperations to be putAsync, the stress tests against index corruption and parallel queries run flawlessly. > It's possible that these particular operation might not need the synchronous flush, but we need to verify if a committed index change is immediately visible to queries. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4567) InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4567?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reopened ISPN-4567: ------------------------------------ > InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running > --------------------------------------------------------------------------------------------- > > Key: ISPN-4567 > URL: https://issues.jboss.org/browse/ISPN-4567 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha5 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.0.0.CR1 > > > {{ManagedDeployableContainer}} detects a running container, even though the previous module killed its server: > {noformat} > [10:25:05] : [org.infinispan:infinispan-as-module-client-integrationtests] kill_server: > [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [echo] Killing Infinispan server with PID - 3658 29739 > [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [delete] Deleting: /mnt/ebs/TeamCity/buildAgent/work/master/integrationtests/as-integration-client/jps.pid > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.infinispan.test.integration.as.InfinispanLuceneDirectoryIT Time elapsed: 3.285 sec <<< ERROR! > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:358) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:88) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4567) InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4567?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4567: ----------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/2876 > InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running > --------------------------------------------------------------------------------------------- > > Key: ISPN-4567 > URL: https://issues.jboss.org/browse/ISPN-4567 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha5 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.0.0.CR1 > > > {{ManagedDeployableContainer}} detects a running container, even though the previous module killed its server: > {noformat} > [10:25:05] : [org.infinispan:infinispan-as-module-client-integrationtests] kill_server: > [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [echo] Killing Infinispan server with PID - 3658 29739 > [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [delete] Deleting: /mnt/ebs/TeamCity/buildAgent/work/master/integrationtests/as-integration-client/jps.pid > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.infinispan.test.integration.as.InfinispanLuceneDirectoryIT Time elapsed: 3.285 sec <<< ERROR! > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:358) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:88) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4567) InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4567?page=com.atlassian.jira.plugin.... ] Galder Zamarreño closed ISPN-4567. ---------------------------------- Resolution: Done https://github.com/infinispan/infinispan/pull/2876 > InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running > --------------------------------------------------------------------------------------------- > > Key: ISPN-4567 > URL: https://issues.jboss.org/browse/ISPN-4567 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha5 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.0.0.CR1 > > > {{ManagedDeployableContainer}} detects a running container, even though the previous module killed its server: > {noformat} > [10:25:05] : [org.infinispan:infinispan-as-module-client-integrationtests] kill_server: > [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [echo] Killing Infinispan server with PID - 3658 29739 > [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [delete] Deleting: /mnt/ebs/TeamCity/buildAgent/work/master/integrationtests/as-integration-client/jps.pid > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.infinispan.test.integration.as.InfinispanLuceneDirectoryIT Time elapsed: 3.285 sec <<< ERROR! > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:358) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:88) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2141) Better configuration options for Infinispan Query

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2141?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2141: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Better configuration options for Infinispan Query > ------------------------------------------------- > > Key: ISPN-2141 > URL: https://issues.jboss.org/browse/ISPN-2141 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.0.0.CR1 > > > Rethink the configuration options for Query. > See also https://community.jboss.org/wiki/InfinispanQuery-DesignAndPlanning -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2342) Cross-Site Replication: State Transfer between sites

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2342?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2342: -------------------------------- Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta2) > Cross-Site Replication: State Transfer between sites > ---------------------------------------------------- > > Key: ISPN-2342 > URL: https://issues.jboss.org/browse/ISPN-2342 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Affects Versions: 6.0.1.Final > Reporter: Erik Salter > Assignee: Pedro Ruivo > Labels: roadmap > Fix For: 7.0.0.CR1, 7.0.0.Final > > > To bring up a new site or recover a failed site, I need an inter-site state transfer mechanism for synchronizing keys. > Note that initially, this should a manual process that is invoked on one site to one of its configured backups. > This should be based on the non-blocking state transfer mechanism for consistency. > The pseudo-design may look similar to the following: > - Manually invokable, background thread > - Since the bridge end is open, there are writes happening to keys. Keep track of the puts/removes on the main data owner. > - Iterate through the key set. > - If the key has already been modified since the process started, discard. > - Else synchronously write the key value in a TX context -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 September 2014