December 2015 - infinispan-issues

[JBoss JIRA] (ISPN-6003) Reduce number of allocations

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6003?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6003: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3871 > Reduce number of allocations > ---------------------------- > > Key: ISPN-6003 > URL: https://issues.jboss.org/browse/ISPN-6003 > Project: Infinispan > Issue Type: Task > Components: Core, Server > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: performance > Fix For: 8.1.0.Final > > > Profiling revealed some allocations that are easy to remove: > * The HotRod operations factory stores a list of flags in a thread-local. The thread-local can be removed, and the flags can be stored in an {{int}}. > * JGroupsTransport copies the list of members to check if a broadcast should be sent as a unicast, and the copy is then discarded. > * ExtendedByteBuf could use {{Array.empty}} instead of {{Array[Byte]()}}. > * DecoratedCache could avoid calling {{Arrays.asList()}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6002) Cache log.isTraceEnabled() as much as possible

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6002?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6002: ------------------------------- Status: Open (was: New) > Cache log.isTraceEnabled() as much as possible > ---------------------------------------------- > > Key: ISPN-6002 > URL: https://issues.jboss.org/browse/ISPN-6002 > Project: Infinispan > Issue Type: Task > Components: Core, Server > Affects Versions: 8.1.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: performance > Fix For: 8.1.0.Final > > > With log4j2 it's not that big of a problem, but there are still environments where this could make a difference (i.e. in the server). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6002) Cache log.isTraceEnabled() as much as possible

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6002?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6002: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3871 > Cache log.isTraceEnabled() as much as possible > ---------------------------------------------- > > Key: ISPN-6002 > URL: https://issues.jboss.org/browse/ISPN-6002 > Project: Infinispan > Issue Type: Task > Components: Core, Server > Affects Versions: 8.1.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: performance > Fix For: 8.1.0.Final > > > With log4j2 it's not that big of a problem, but there are still environments where this could make a difference (i.e. in the server). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-15) Update to Spark 1.5

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-15?page=com.atlassian.jira.plugin.s... ] Gustavo Fernandes updated ISPRK-15: ----------------------------------- Status: Open (was: New) > Update to Spark 1.5 > ------------------- > > Key: ISPRK-15 > URL: https://issues.jboss.org/browse/ISPRK-15 > Project: Infinispan Spark > Issue Type: Component Upgrade > Affects Versions: 0.1 > Reporter: Gustavo Fernandes > Fix For: 0.2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-15) Update to Spark 1.5

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-15?page=com.atlassian.jira.plugin.s... ] Gustavo Fernandes updated ISPRK-15: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-spark/pull/15 > Update to Spark 1.5 > ------------------- > > Key: ISPRK-15 > URL: https://issues.jboss.org/browse/ISPRK-15 > Project: Infinispan Spark > Issue Type: Component Upgrade > Affects Versions: 0.1 > Reporter: Gustavo Fernandes > Fix For: 0.2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5974) Continuous query should support projections

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5974?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5974: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1287398|https://bugzilla.redhat.com/show_bug.cgi?id=1287398] from ON_QA to VERIFIED > Continuous query should support projections > ------------------------------------------- > > Key: ISPN-5974 > URL: https://issues.jboss.org/browse/ISPN-5974 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Final, 8.0.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6008) Query DSL orderBy should only accept single-valued properties

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6008: ----------------------------------- Summary: Query DSL orderBy should only accept single-valued properties Key: ISPN-6008 URL: https://issues.jboss.org/browse/ISPN-6008 Project: Infinispan Issue Type: Bug Components: Embedded Querying, Remote Querying Affects Versions: 8.0.2.Final, 8.1.0.CR1 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 8.1.0.Final, 8.0.3.Final {code} QueryFactory qf = getQueryFactory(); Query q = qf.from(getModelFactory().getUserImplClass()) .select(Expression.min("name")) .groupBy("addresses.street") .build(); q.list(); {code} Should throw an exception during query parsing because property "addresses.street" is not single-valued. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5974) Continuous query should support projections

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5974?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5974: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Continuous query should support projections > ------------------------------------------- > > Key: ISPN-5974 > URL: https://issues.jboss.org/browse/ISPN-5974 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Final, 8.0.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5623) Retried prepare commands do not wait for backup locks

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5623?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5623: ----------------------------------------------- Pedro Ruivo <pruivo(a)redhat.com> changed the Status of [bug 1245500|https://bugzilla.redhat.com/show_bug.cgi?id=1245500] from ASSIGNED to POST > Retried prepare commands do not wait for backup locks > ----------------------------------------------------- > > Key: ISPN-5623 > URL: https://issues.jboss.org/browse/ISPN-5623 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.3.Final, 8.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Fix For: 8.1.0.Final > > Attachments: OptimisticPrimaryOwnerCrashDuringPrepareTest.java > > > When the primary owner crashes during prepare, the prepare command is retried on the new primary owner. But because the transaction topology id stays the same, the new primary owner does not check for backup locks owned by other transactions from the previous topology. > That makes it possible for the retried prepare command to lock a key that was already locked by another transaction on the primary owner. > This wasn't a problem before the ISPN-4546 fix, because a primary owner crash would have forced the transaction to roll back. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5889) Merge views not dealt with in Hot Rod server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5889?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5889: ----------------------------------------------- Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1274155|https://bugzilla.redhat.com/show_bug.cgi?id=1274155] from ON_QA to VERIFIED > Merge views not dealt with in Hot Rod server > -------------------------------------------- > > Key: ISPN-5889 > URL: https://issues.jboss.org/browse/ISPN-5889 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 8.0.1.Final, 8.1.0.Alpha2 > Reporter: Galder Zamarreño > Assignee: Dan Berindei > Fix For: 8.1.0.CR1, 8.1.0.Final > > > Hot Rod server does not deal with merge views, so when members return back to the cluster, the view is not updated. The Hot Rod server view change listener currently only deals with nodes leaving or crashing. This problem is not a big one since it just means that until the next view change happens, clients will work with a reduced view, working in a suboptimal way, but it won't have correctness impact. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2015