December 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5858) ValueMatcher and AvailabilityMode should have externalizers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5858?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5858: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1272390|https://bugzilla.redhat.com/show_bug.cgi?id=1272390] from ON_QA to ASSIGNED > ValueMatcher and AvailabilityMode should have externalizers > ----------------------------------------------------------- > > Key: ISPN-5858 > URL: https://issues.jboss.org/browse/ISPN-5858 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.0.1.Final, 8.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Alpha2, 8.1.0.CR1 > > > The default enum serialization is pretty bad, it writes both the enum name and value name as strings. > {{ValueMatcher}} is needed in each write command, so we should optimize it. > {{AvailabilityMode}} doesn't matter that much, except when the coordinator changes, and the new coordinator has to retrieve the status of all the caches on all the nodes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5859) HotRod server should not use privileged actions for common stuff

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5859?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5859: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1272390|https://bugzilla.redhat.com/show_bug.cgi?id=1272390] from ON_QA to ASSIGNED > HotRod server should not use privileged actions for common stuff > ---------------------------------------------------------------- > > Key: ISPN-5859 > URL: https://issues.jboss.org/browse/ISPN-5859 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.0.1.Final, 8.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Alpha2, 8.1.0.Final > > > The HotRod server uses privileged actions to perform operations that are needed for each request, like reading the cache mode to decide what kind (if any) topology update to send to the client. Since privileged actions use thread-locals, we should try to avoid them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5860) ComponentRegistry should cache the VersionGenerator in a field

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5860?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5860: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1272390|https://bugzilla.redhat.com/show_bug.cgi?id=1272390] from ON_QA to ASSIGNED > ComponentRegistry should cache the VersionGenerator in a field > -------------------------------------------------------------- > > Key: ISPN-5860 > URL: https://issues.jboss.org/browse/ISPN-5860 > Project: Infinispan > Issue Type: Bug > Components: Core, Server > Affects Versions: 8.0.1.Final, 8.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Alpha2, 8.1.0.Final > > > The {{VersionGenerator}} component is read by the HotRod server for each write operation, and we can optimize it by caching the component in a field. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5857) HotRod client should use the consistent hash in replicated mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5857?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5857: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1272390|https://bugzilla.redhat.com/show_bug.cgi?id=1272390] from ON_QA to ASSIGNED > HotRod client should use the consistent hash in replicated mode > --------------------------------------------------------------- > > Key: ISPN-5857 > URL: https://issues.jboss.org/browse/ISPN-5857 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.0.1.Final, 8.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: hotrod > Fix For: 8.1.0.Alpha2, 8.1.0.Final > > > The HotRod server assumes that in replicated mode the server accessed by the client doesn't matter, so it doesn't send a consistent hash in the topology updates. > However, since replicated mode is now implemented on top of distributed mode, hitting the primary owner or another node makes a big difference. We should change the server to send the consistent hash for replicated caches as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-6003?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-6003: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1272390|https://bugzilla.redhat.com/show_bug.cgi?id=1272390] from ON_QA to ASSIGNED > 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, 11 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-6002?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-6002: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1272390|https://bugzilla.redhat.com/show_bug.cgi?id=1272390] from ON_QA to ASSIGNED > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5497) MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue, MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent and MetadataAPIDefaultExpiryTest.testDefaultLifespanReplace fail randomly

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5497?page=com.atlassian.jira.plugin.... ] Roman Macor updated ISPN-5497: ------------------------------ Summary: MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue, MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent and MetadataAPIDefaultExpiryTest.testDefaultLifespanReplace fail randomly (was: MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue and MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent fail randomly) > MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue, MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent and MetadataAPIDefaultExpiryTest.testDefaultLifespanReplace fail randomly > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5497 > URL: https://issues.jboss.org/browse/ISPN-5497 > Project: Infinispan > Issue Type: Bug > Affects Versions: 7.2.1.Final > Reporter: Roman Macor > Assignee: Dan Berindei > Fix For: 8.1.0.Alpha1, 8.1.0.Final, 8.0.2.Final > > > MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent and MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue fail randomly with assertion error > org.infinispan.api.MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue > Error Message > expected:<v11> but was:<null> > Stacktrace > java.lang.AssertionError: expected:<v11> but was:<null> > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:101) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:108) > at org.infinispan.api.MetadataAPIDefaultExpiryTest.expectCachedThenExpired(MetadataAPIDefaultExpiryTest.java:85) > at org.infinispan.api.MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue(MetadataAPIDefaultExpiryTest.java:49) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > org.infinispan.api.MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent > Error Message > expected:<v1> but was:<null> > Stacktrace > java.lang.AssertionError: expected:<v1> but was:<null> > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:101) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:108) > at org.infinispan.api.MetadataAPIDefaultExpiryTest.expectCachedThenExpired(MetadataAPIDefaultExpiryTest.java:85) > at org.infinispan.api.MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent(MetadataAPIDefaultExpiryTest.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6021) COUNT and AVG aggregations for fields of embedded entities doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-6021?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-6021: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1274769 Bugzilla Update: Perform > COUNT and AVG aggregations for fields of embedded entities doesn't work > ----------------------------------------------------------------------- > > Key: ISPN-6021 > URL: https://issues.jboss.org/browse/ISPN-6021 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final, 8.0.2.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Alpha1, 8.2.0.Final, 8.0.3.Final, 8.1.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6021) COUNT and AVG aggregations for fields of embedded entities doesn't work

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6021?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-6021: ------------------------------------- It seems the fix for ISPN-5682 took care of only some of the aggregation functions. COUNT and AVG were not fixed but the problem escaped through the cracks of the test suite. > COUNT and AVG aggregations for fields of embedded entities doesn't work > ----------------------------------------------------------------------- > > Key: ISPN-6021 > URL: https://issues.jboss.org/browse/ISPN-6021 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final, 8.0.2.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Alpha1, 8.2.0.Final, 8.0.3.Final, 8.1.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6021) COUNT and AVG aggregations for fields of embedded entities doesn't work

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6021?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6021: -------------------------------- Fix Version/s: 8.1.1.Final > COUNT and AVG aggregations for fields of embedded entities doesn't work > ----------------------------------------------------------------------- > > Key: ISPN-6021 > URL: https://issues.jboss.org/browse/ISPN-6021 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final, 8.0.2.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Alpha1, 8.2.0.Final, 8.0.3.Final, 8.1.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 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 December 2015