May 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3952) Upgrade to Hibernate Search 4.5.0.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3952?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3952: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1083737|https://bugzilla.redhat.com/show_bug.cgi?id=1083737] from ASSIGNED to MODIFIED > Upgrade to Hibernate Search 4.5.0.Final > --------------------------------------- > > Key: ISPN-3952 > URL: https://issues.jboss.org/browse/ISPN-3952 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: 630 > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3934) Upgrade to Hibernate Search 4.5.0.CR1 and HQL-Parser 1.0.0.Alpha6

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3934?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3934: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1083737|https://bugzilla.redhat.com/show_bug.cgi?id=1083737] from ASSIGNED to MODIFIED > Upgrade to Hibernate Search 4.5.0.CR1 and HQL-Parser 1.0.0.Alpha6 > ----------------------------------------------------------------- > > Key: ISPN-3934 > URL: https://issues.jboss.org/browse/ISPN-3934 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: 630 > Fix For: 7.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3891) Tune for batching without transactions

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3891?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-3891: --------------------------------------- That would be very nice too! You have to if the isolation level is promising repeatable read in the scope of the current TX, but I guess you could decide depending on configuration and isolation levels. > Tune for batching without transactions > -------------------------------------- > > Key: ISPN-3891 > URL: https://issues.jboss.org/browse/ISPN-3891 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Fix For: 7.0.0.Beta1, 7.0.0.Final > > > The usage of batching is a critically important feature, widely used to improve performance in many common scenarios, but while documentation makes it clear that it's built on transactions, it's unclear how these transactions should be configured. > Also, I would challenge the decision of building batching on top of transactions and see if there are opportunities for further optimization. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3891) Tune for batching without transactions

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3891?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-3891: ------------------------------------ I was thinking of attacking the problem from the other angle: try to decouple Infinispan transaction support from the transaction manager. It should be possible to execute an implicit transaction without registering the transaction with the TM, e.g. when the user calls {{cache.get(k)}} we shouldn't talk to the TM at all. > Tune for batching without transactions > -------------------------------------- > > Key: ISPN-3891 > URL: https://issues.jboss.org/browse/ISPN-3891 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Fix For: 7.0.0.Beta1, 7.0.0.Final > > > The usage of batching is a critically important feature, widely used to improve performance in many common scenarios, but while documentation makes it clear that it's built on transactions, it's unclear how these transactions should be configured. > Also, I would challenge the decision of building batching on top of transactions and see if there are opportunities for further optimization. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4293) PR for ISPN-4137 causes a performance drop in repl tx mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4293?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4293: ----------------------------------------------- Dan Berindei <dberinde(a)redhat.com> changed the Status of [bug 1098463|https://bugzilla.redhat.com/show_bug.cgi?id=1098463] from POST to MODIFIED > PR for ISPN-4137 causes a performance drop in repl tx mode > ---------------------------------------------------------- > > Key: ISPN-4293 > URL: https://issues.jboss.org/browse/ISPN-4293 > Project: Infinispan > Issue Type: Bug > Reporter: Jakub Markos > Assignee: Dan Berindei > Fix For: 7.0.0.Beta1 > > > See the last graph here for example http://jawa36.mw.lab.eng.brq.redhat.com:8080/repo/reports/metric/saved/te... > Caused by this commit https://github.com/infinispan/infinispan/commit/8be817a193699ce8b59aec8da... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4108) Pessimistic tx for a union CH will not be forwarded to all owners.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4108?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4108: ----------------------------------------------- Dan Berindei <dberinde(a)redhat.com> changed the Status of [bug 1102048|https://bugzilla.redhat.com/show_bug.cgi?id=1102048] from POST to MODIFIED > Pessimistic tx for a union CH will not be forwarded to all owners. > ------------------------------------------------------------------ > > Key: ISPN-4108 > URL: https://issues.jboss.org/browse/ISPN-4108 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 5.2.7.Final > Reporter: Erik Salter > Assignee: Dan Berindei > Fix For: 7.0.0.Beta1 > > > There is a case where transactions originating from a LockControlCommand will not be forwarded to the new owner during state transfer. > If the transactions begin on the old primary owner after the tx list was sent to the new owner, the lock information may not be replicated to the joiner because the originator is still the primary owner in the union CH that we use during state transfer. When state transfer ends and the joiner becomes the new primary owner, it will allow other txs to lock the same key. This leads to data loss/inconsistency. > We should change PessimisticLockingInterceptor to replicate the lock command to the other owners even if the originator is the primary owner when there is a state transfer in progress. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4091) Transactions and data should prefer to be sourced from a primary owner

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4091?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4091: ----------------------------------------------- Dan Berindei <dberinde(a)redhat.com> changed the Status of [bug 1102048|https://bugzilla.redhat.com/show_bug.cgi?id=1102048] from POST to MODIFIED > Transactions and data should prefer to be sourced from a primary owner > ---------------------------------------------------------------------- > > Key: ISPN-4091 > URL: https://issues.jboss.org/browse/ISPN-4091 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 5.2.7.Final > Reporter: Erik Salter > Assignee: Dan Berindei > Fix For: 7.0.0.Beta1 > > > The current state transfer mechanism will ask the backup segments for transaction and state information. However, this breaks if there is a pessimistic transaction executing on the primary data owner, Consider the following use case: > A new owner joins and sources the ongoing transactions and data for key k from the backup. Meanwhile, a local transaction has started on the primary owner for k, but has not prepared on any remote nodes. So the new node does not know about the ongoing transaction. While that's going on, a new tx starts on the new owner. Since these are pessimistic, the new transaction will acquires the lock for the same key. > So we can have data inconsistency. > The state transfer mechanism should prefer to source the transaction and state information from the primary owner. This should cover all cases: if the originator is not the primary owner, then any (backup) locks must be replicated to all the owners, either directly during the tx or during a previous state transfer. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4331) Add searching for TransactionManager in OSGi to GenericTransactionManagerLookup

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4331?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-4331: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2588 > Add searching for TransactionManager in OSGi to GenericTransactionManagerLookup > ------------------------------------------------------------------------------- > > Key: ISPN-4331 > URL: https://issues.jboss.org/browse/ISPN-4331 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Affects Versions: 7.0.0.Alpha4 > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 7.0.0.Beta1 > > > The current implementation is not able to find the transaction manager that is embedded in Apache Karaf. > Apache Karaf includes Apache Aries and after installing optional feature "transaction" by "feature:install transaction", the transaction manager is available through JNDI. We just need to check the right address. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4331) Add searching for TransactionManager in OSGi to GenericTransactionManagerLookup

by Martin Gencur (JIRA)

Martin Gencur created ISPN-4331: ----------------------------------- Summary: Add searching for TransactionManager in OSGi to GenericTransactionManagerLookup Key: ISPN-4331 URL: https://issues.jboss.org/browse/ISPN-4331 Project: Infinispan Issue Type: Feature Request Components: Transactions Affects Versions: 7.0.0.Alpha4 Reporter: Martin Gencur Assignee: Martin Gencur Fix For: 7.0.0.Beta1 The current implementation is not able to find the transaction manager that is embedded in Apache Karaf. Apache Karaf includes Apache Aries and after installing optional feature "transaction" by "feature:install transaction", the transaction manager is available through JNDI. We just need to check the right address. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4330) Add test for distributed HotRod RollingUpgrades scenario

by Tomas Sykora (JIRA)

Tomas Sykora created ISPN-4330: ---------------------------------- Summary: Add test for distributed HotRod RollingUpgrades scenario Key: ISPN-4330 URL: https://issues.jboss.org/browse/ISPN-4330 Project: Infinispan Issue Type: Task Components: Test Suite - Server Reporter: Tomas Sykora Assignee: Tomas Sykora Test scenario with at least 2 source and 2 target nodes with clustered configuration. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2014