February 2017 - infinispan-issues

[JBoss JIRA] (ISPN-7507) Deprecate asynchronous options for transactional cache

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-7507: --------------------------------- Summary: Deprecate asynchronous options for transactional cache Key: ISPN-7507 URL: https://issues.jboss.org/browse/ISPN-7507 Project: Infinispan Issue Type: Sub-task Components: Core, Transactions Reporter: Pedro Ruivo Assignee: Pedro Ruivo The following options are going to be removed: * sync-commit-phase * sync-rollback-phase * mode="ASYNC" (this will be transformed in SYNC mode) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7499) ProtobufMetadataManager methods should throw an error if the requested file was not found

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7499?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7499. -------------------------------- Resolution: Done > ProtobufMetadataManager methods should throw an error if the requested file was not found > ----------------------------------------------------------------------------------------- > > Key: ISPN-7499 > URL: https://issues.jboss.org/browse/ISPN-7499 > 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.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7433) Investigate performance with different xmit_interval values

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7433?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7433: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Investigate performance with different xmit_interval values > ----------------------------------------------------------- > > Key: ISPN-7433 > URL: https://issues.jboss.org/browse/ISPN-7433 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: performance > Fix For: 9.0.0.CR2 > > > The default {{UNICAST3.xmit_interval}} is 500ms, and the default {{NAKACK2.xmit_interval}} is 1000ms. According to Bela, a {{xmit_interval}} of 100ms should be much better for performance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7506) Tests fail after upgrading Lucene version

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7506?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7506: ------------------------------------ Status: Open (was: New) > Tests fail after upgrading Lucene version > ----------------------------------------- > > Key: ISPN-7506 > URL: https://issues.jboss.org/browse/ISPN-7506 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > > Upgrading Lucene causes clash with the elasticsearch being used in tests: > {noformat} > org.infinispan.test.integration.as (1) > query.ElasticsearchIndexManagerIT > java.lang.AssertionError: Version must be upgraded to [5.5.4] is still set to [5.5.2] > at org.elasticsearch.Version.(Version.java:316) > at org.infinispan.query.test.elasticsearch.ElasticSearchCluster$TestNode.(ElasticSearchCluster.java:59) > at org.infinispan.query.test.elasticsearch.ElasticSearchCluster$ElasticSearchClusterBuilder.buildNode(ElasticSearchCluster.java:123) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7506) Tests fail after upgrading Lucene version

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7506?page=com.atlassian.jira.plugin.... ] Work on ISPN-7506 started by Gustavo Fernandes. ----------------------------------------------- > Tests fail after upgrading Lucene version > ----------------------------------------- > > Key: ISPN-7506 > URL: https://issues.jboss.org/browse/ISPN-7506 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > Upgrading Lucene causes clash with the elasticsearch being used in tests: > {noformat} > org.infinispan.test.integration.as (1) > query.ElasticsearchIndexManagerIT > java.lang.AssertionError: Version must be upgraded to [5.5.4] is still set to [5.5.2] > at org.elasticsearch.Version.(Version.java:316) > at org.infinispan.query.test.elasticsearch.ElasticSearchCluster$TestNode.(ElasticSearchCluster.java:59) > at org.infinispan.query.test.elasticsearch.ElasticSearchCluster$ElasticSearchClusterBuilder.buildNode(ElasticSearchCluster.java:123) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7506) Tests fail after upgrading Lucene version

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-7506: --------------------------------------- Summary: Tests fail after upgrading Lucene version Key: ISPN-7506 URL: https://issues.jboss.org/browse/ISPN-7506 Project: Infinispan Issue Type: Bug Reporter: Gustavo Fernandes Upgrading Lucene causes clash with the elasticsearch being used in tests: {noformat} org.infinispan.test.integration.as (1) query.ElasticsearchIndexManagerIT java.lang.AssertionError: Version must be upgraded to [5.5.4] is still set to [5.5.2] at org.elasticsearch.Version.(Version.java:316) at org.infinispan.query.test.elasticsearch.ElasticSearchCluster$TestNode.(ElasticSearchCluster.java:59) at org.infinispan.query.test.elasticsearch.ElasticSearchCluster$ElasticSearchClusterBuilder.buildNode(ElasticSearchCluster.java:123) {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7505) Non-functional read in transaction with modifications returns old value

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-7505?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-7505: ------------------------------ Component/s: Core > Non-functional read in transaction with modifications returns old value > ----------------------------------------------------------------------- > > Key: ISPN-7505 > URL: https://issues.jboss.org/browse/ISPN-7505 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR1 > Reporter: Radim Vansa > Assignee: Radim Vansa > > See this modified FunctionalTxInMemoryTest: > {code:java} > @Test(dataProvider = "owningModeAndReadWrites") > public void testReadWriteAfterMods(boolean isOwner, WriteMethod method) throws Exception { > Object KEY = getKey(isOwner); > cache(0, DIST).put(KEY, "a"); > tm.begin(); > assertEquals("a", rw.eval(KEY, append("b")).join()); > assertEquals("ab", rw.evalMany(Collections.singleton(KEY), append("c")).findAny().get()); > assertEquals("abc", cache(0, DIST).get(KEY)); // <-- THIS FAILS > assertEquals(null, rw.eval("otherKey", append("d")).join()); > assertEquals("abc", method.action.eval(KEY, wo, rw, > MarshallableFunctions.returnReadOnlyFindOrNull(), > (BiConsumer<EntryView.WriteEntryView<String>, String> & Serializable) (e, prev) -> {}, getClass())); > tm.commit(); > } > {code} > When the entry was modified in given transaction, we have to do the read using functional identity read which passes all modifications along. We need to do this for all {{remoteGet}} s, including those invoked for {{putIfAbsent}} etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7505) Non-functional read in transaction with modifications returns old value

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-7505?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-7505: ------------------------------ Affects Version/s: 9.0.0.CR1 > Non-functional read in transaction with modifications returns old value > ----------------------------------------------------------------------- > > Key: ISPN-7505 > URL: https://issues.jboss.org/browse/ISPN-7505 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.CR1 > Reporter: Radim Vansa > Assignee: Radim Vansa > > See this modified FunctionalTxInMemoryTest: > {code:java} > @Test(dataProvider = "owningModeAndReadWrites") > public void testReadWriteAfterMods(boolean isOwner, WriteMethod method) throws Exception { > Object KEY = getKey(isOwner); > cache(0, DIST).put(KEY, "a"); > tm.begin(); > assertEquals("a", rw.eval(KEY, append("b")).join()); > assertEquals("ab", rw.evalMany(Collections.singleton(KEY), append("c")).findAny().get()); > assertEquals("abc", cache(0, DIST).get(KEY)); // <-- THIS FAILS > assertEquals(null, rw.eval("otherKey", append("d")).join()); > assertEquals("abc", method.action.eval(KEY, wo, rw, > MarshallableFunctions.returnReadOnlyFindOrNull(), > (BiConsumer<EntryView.WriteEntryView<String>, String> & Serializable) (e, prev) -> {}, getClass())); > tm.commit(); > } > {code} > When the entry was modified in given transaction, we have to do the read using functional identity read which passes all modifications along. We need to do this for all {{remoteGet}} s, including those invoked for {{putIfAbsent}} etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7505) Non-functional read in transaction with modifications returns old value

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-7505?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-7505: ------------------------------ Description: See this modified FunctionalTxInMemoryTest: {code:java} @Test(dataProvider = "owningModeAndReadWrites") public void testReadWriteAfterMods(boolean isOwner, WriteMethod method) throws Exception { Object KEY = getKey(isOwner); cache(0, DIST).put(KEY, "a"); tm.begin(); assertEquals("a", rw.eval(KEY, append("b")).join()); assertEquals("ab", rw.evalMany(Collections.singleton(KEY), append("c")).findAny().get()); assertEquals("abc", cache(0, DIST).get(KEY)); // <-- THIS FAILS assertEquals(null, rw.eval("otherKey", append("d")).join()); assertEquals("abc", method.action.eval(KEY, wo, rw, MarshallableFunctions.returnReadOnlyFindOrNull(), (BiConsumer<EntryView.WriteEntryView<String>, String> & Serializable) (e, prev) -> {}, getClass())); tm.commit(); } {code} When the entry was modified in given transaction, we have to do the read using functional identity read which passes all modifications along. We need to do this for all {{remoteGet}} s, including those invoked for {{putIfAbsent}} etc. was: See this modified FunctionalTxInMemoryTest: {code:java} @Test(dataProvider = "owningModeAndReadWrites") public void testReadWriteAfterMods(boolean isOwner, WriteMethod method) throws Exception { Object KEY = getKey(isOwner); cache(0, DIST).put(KEY, "a"); tm.begin(); assertEquals("a", rw.eval(KEY, append("b")).join()); assertEquals("ab", rw.evalMany(Collections.singleton(KEY), append("c")).findAny().get()); assertEquals("abc", cache(0, DIST).get(KEY)); // <-- THIS FAILS assertEquals(null, rw.eval("otherKey", append("d")).join()); assertEquals("abc", method.action.eval(KEY, wo, rw, MarshallableFunctions.returnReadOnlyFindOrNull(), (BiConsumer<EntryView.WriteEntryView<String>, String> & Serializable) (e, prev) -> {}, getClass())); tm.commit(); } {code} When the entry was modified in given transaction, we have to do the read using functional identity read which passes all modifications along. We need to do this for all {{remoteGet}}s, including those invoked for {{putIfAbsent}} etc. > Non-functional read in transaction with modifications returns old value > ----------------------------------------------------------------------- > > Key: ISPN-7505 > URL: https://issues.jboss.org/browse/ISPN-7505 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.CR1 > Reporter: Radim Vansa > Assignee: Radim Vansa > > See this modified FunctionalTxInMemoryTest: > {code:java} > @Test(dataProvider = "owningModeAndReadWrites") > public void testReadWriteAfterMods(boolean isOwner, WriteMethod method) throws Exception { > Object KEY = getKey(isOwner); > cache(0, DIST).put(KEY, "a"); > tm.begin(); > assertEquals("a", rw.eval(KEY, append("b")).join()); > assertEquals("ab", rw.evalMany(Collections.singleton(KEY), append("c")).findAny().get()); > assertEquals("abc", cache(0, DIST).get(KEY)); // <-- THIS FAILS > assertEquals(null, rw.eval("otherKey", append("d")).join()); > assertEquals("abc", method.action.eval(KEY, wo, rw, > MarshallableFunctions.returnReadOnlyFindOrNull(), > (BiConsumer<EntryView.WriteEntryView<String>, String> & Serializable) (e, prev) -> {}, getClass())); > tm.commit(); > } > {code} > When the entry was modified in given transaction, we have to do the read using functional identity read which passes all modifications along. We need to do this for all {{remoteGet}} s, including those invoked for {{putIfAbsent}} etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7505) Non-functional read in transaction with modifications returns old value

by Radim Vansa (JIRA)

Radim Vansa created ISPN-7505: --------------------------------- Summary: Non-functional read in transaction with modifications returns old value Key: ISPN-7505 URL: https://issues.jboss.org/browse/ISPN-7505 Project: Infinispan Issue Type: Bug Reporter: Radim Vansa Assignee: Radim Vansa See this modified FunctionalTxInMemoryTest: {code:java} @Test(dataProvider = "owningModeAndReadWrites") public void testReadWriteAfterMods(boolean isOwner, WriteMethod method) throws Exception { Object KEY = getKey(isOwner); cache(0, DIST).put(KEY, "a"); tm.begin(); assertEquals("a", rw.eval(KEY, append("b")).join()); assertEquals("ab", rw.evalMany(Collections.singleton(KEY), append("c")).findAny().get()); assertEquals("abc", cache(0, DIST).get(KEY)); // <-- THIS FAILS assertEquals(null, rw.eval("otherKey", append("d")).join()); assertEquals("abc", method.action.eval(KEY, wo, rw, MarshallableFunctions.returnReadOnlyFindOrNull(), (BiConsumer<EntryView.WriteEntryView<String>, String> & Serializable) (e, prev) -> {}, getClass())); tm.commit(); } {code} When the entry was modified in given transaction, we have to do the read using functional identity read which passes all modifications along. We need to do this for all {{remoteGet}}s, including those invoked for {{putIfAbsent}} etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2017