April 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9083) Remove support for 'indexed_by_default' option in protobuf schemas

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-9083?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-9083: -------------------------------- Description: All the behaviour around this option must be removed and the option must be documented as no longer supported in Infinispan 10. Usage of this option must trigger a warning. Should be entirely removed in 10.1 or some later version right after 10. was: All the behaviour around it must be removed and the options must be documented as no longer supported. Usage of this option must trigger a warning. > Remove support for 'indexed_by_default' option in protobuf schemas > ------------------------------------------------------------------ > > Key: ISPN-9083 > URL: https://issues.jboss.org/browse/ISPN-9083 > Project: Infinispan > Issue Type: Task > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 10.0.0.Final > > > All the behaviour around this option must be removed and the option must be documented as no longer supported in Infinispan 10. > Usage of this option must trigger a warning. Should be entirely removed in 10.1 or some later version right after 10. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9083) Remove support for 'indexed_by_default' option in protobuf schemas

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-9083?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-9083: -------------------------------- Description: All the behaviour around this option must be removed and the option must be documented as no longer supported in Infinispan 10. Usage of this option must trigger a warning. Should be entirely removed in 10.1 or some later version right after 10 - usages will be ignored after this point. was: All the behaviour around this option must be removed and the option must be documented as no longer supported in Infinispan 10. Usage of this option must trigger a warning. Should be entirely removed in 10.1 or some later version right after 10. > Remove support for 'indexed_by_default' option in protobuf schemas > ------------------------------------------------------------------ > > Key: ISPN-9083 > URL: https://issues.jboss.org/browse/ISPN-9083 > Project: Infinispan > Issue Type: Task > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 10.0.0.Final > > > All the behaviour around this option must be removed and the option must be documented as no longer supported in Infinispan 10. > Usage of this option must trigger a warning. Should be entirely removed in 10.1 or some later version right after 10 - usages will be ignored after this point. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9083) Remove support for 'indexed_by_default' option in protobuf schemas

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-9083?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-9083: -------------------------------- Fix Version/s: 10.0.0.Final > Remove support for 'indexed_by_default' option in protobuf schemas > ------------------------------------------------------------------ > > Key: ISPN-9083 > URL: https://issues.jboss.org/browse/ISPN-9083 > Project: Infinispan > Issue Type: Task > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 10.0.0.Final > > > All the behaviour around it must be removed and the options must be documented as no longer supported. > Usage of this option must trigger a warning. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9083) Remove support for 'indexed_by_default' option in protobuf schemas

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-9083?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned ISPN-9083: ----------------------------------- Assignee: Adrian Nistor > Remove support for 'indexed_by_default' option in protobuf schemas > ------------------------------------------------------------------ > > Key: ISPN-9083 > URL: https://issues.jboss.org/browse/ISPN-9083 > Project: Infinispan > Issue Type: Task > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > All the behaviour around it must be removed and the options must be documented as no longer supported. > Usage of this option must trigger a warning. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9083) Remove support for 'indexed_by_default' option in protobuf schemas

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-9083: ----------------------------------- Summary: Remove support for 'indexed_by_default' option in protobuf schemas Key: ISPN-9083 URL: https://issues.jboss.org/browse/ISPN-9083 Project: Infinispan Issue Type: Task Reporter: Adrian Nistor All the behaviour around it must be removed and the options must be documented as no longer supported. Usage of this option must trigger a warning. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9083) Remove support for 'indexed_by_default' option in protobuf schemas

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-9083?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-9083: -------------------------------- Status: Open (was: New) > Remove support for 'indexed_by_default' option in protobuf schemas > ------------------------------------------------------------------ > > Key: ISPN-9083 > URL: https://issues.jboss.org/browse/ISPN-9083 > Project: Infinispan > Issue Type: Task > Reporter: Adrian Nistor > > All the behaviour around it must be removed and the options must be documented as no longer supported. > Usage of this option must trigger a warning. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9063) Average stats should be calculated in Nanoseconds but exposed in Milliseconds

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9063?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9063: ------------------------------- Sprint: Sprint 9.3.0.Alpha1 > Average stats should be calculated in Nanoseconds but exposed in Milliseconds > ----------------------------------------------------------------------------- > > Key: ISPN-9063 > URL: https://issues.jboss.org/browse/ISPN-9063 > Project: Infinispan > Issue Type: Bug > Components: Console, JMX, reporting and management > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.2.Final, 9.3.0.Alpha1 > > > ISPN-7768 changed the precision of the exposed average-<read|write>time stats from Milliseconds to Nanoseconds. This causes backwards compatibility issues with previous versions of Infinispan and JDG. Therefore we need to ensure that these stats are exposed to the user in Milliseconds, however they should still be calculated in Nanoseconds internally to improve accuracy and avoid rounding errors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9046) Average stats should be represented in milliseconds

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9046?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-9046. -------------------------------- Resolution: Duplicate Issue > Average stats should be represented in milliseconds > --------------------------------------------------- > > Key: ISPN-9046 > URL: https://issues.jboss.org/browse/ISPN-9046 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Alpha1 > > > ISPN-7768 should be reverted to ensure backwards compatibility with JDG versions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9032) OperationsDuringMergeConflictTest.testPartitionMergePolicy random failures

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9032?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9032: ------------------------------- Sprint: Sprint 9.3.0.Alpha1 > OperationsDuringMergeConflictTest.testPartitionMergePolicy random failures > -------------------------------------------------------------------------- > > Key: ISPN-9032 > URL: https://issues.jboss.org/browse/ISPN-9032 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Ryan Emerson > Labels: testsuite_stability > Fix For: 9.3.0.Alpha1 > > > The test modifies a key in both partitions and checks that each partition still sees its own value for a while after receiving the [merged cluster view|https://github.com/infinispan/infinispan/blob/ee87349f0b134b53b3090f...]. > It installs a {{BlockStateResponseCommandHandler}} to block the conflict resolution responses and to keep the pre-merge values in the non-preferred topology owners. However, it does not block the installation of the {{CONFLICT_RESOLUTION}} cache topology. And during conflict resolution the read CH is the preferred topology's read CH, so non-preferred topology owners will ask the primary owner for the value: > {noformat} > 17:12:07,088 INFO (testng-Test:[]) [JGroupsTransport] ISPN000093: Received new, MERGED cluster view for channel ISPN: MergeView::[Test-NodeI-48950|10] (4) [Test-NodeI-48950, Test-NodeJ-6577, Test-NodeK-2872, Test-NodeL-23686], 2 subgroups: [Test-NodeI-48950|8] (2) [Test-NodeI-48950, Test-NodeJ-6577], [Test-NodeK-2872|9] (2) [Test-NodeK-2872, Test-NodeL-23686] > 17:12:07,134 TRACE (stateTransferExecutor-thread-Test-NodeI-p50536-t2:[Merge-10]) [DefaultConflictManager] Cache ___defaultcache attempting to receive all replicas for segment 0 with topology CacheTopology{id=20, rebalanceId=7, currentCH=DefaultConsistentHash{ns=256, owners = (2)[Test-NodeK-2872: 134+122, Test-NodeL-23686: 122+134]}, pendingCH=DefaultConsistentHash{ns=256, owners = (4)[Test-NodeK-2872: 134+122, Test-NodeL-23686: 122+134, Test-NodeI-48950: 0+256, Test-NodeJ-6577: 0+256]}, unionCH=DefaultConsistentHash{ns=256, owners = (4)[Test-NodeK-2872: 134+122, Test-NodeL-23686: 122+134, Test-NodeI-48950: 0+256, Test-NodeJ-6577: 0+256]}, phase=CONFLICT_RESOLUTION, actualMembers=[Test-NodeK-2872, Test-NodeL-23686, Test-NodeI-48950, Test-NodeJ-6577], persistentUUIDs=[40b58191-37f1-4fa4-8e4b-f1a7c17bfa59, 208d742d-ecc9-4792-9dd5-f74d5666f5a2, d8914096-a5a4-4e1e-95a0-27c50fee9999, 7464e58b-5e23-4c1b-909e-4e53055f12ca]} > 17:12:07,212 TRACE (testng-Test:[]) [BaseDistributionInterceptor] Perform remote get for key MagicKey{13A4/DDFB0E77/56@Test-NodeI-48950}. currentTopologyId=20, owners=[Test-NodeK-2872, Test-NodeL-23686] > 17:12:07,212 TRACE (testng-Test:[]) [RpcManagerImpl] Test-NodeI-48950 invoking ClusteredGetCommand{key=MagicKey{13A4/DDFB0E77/56@Test-NodeI-48950}, flags=[]} to recipient list [Test-NodeK-2872, Test-NodeL-23686] with options RpcOptions{timeout=15000, unit=MILLISECONDS, deliverOrder=NONE, responseFilter=org.infinispan.interceptors.impl.BaseRpcInterceptor$1@241e783a, responseMode=WAIT_FOR_VALID_RESPONSE} > 17:12:07,225 TRACE (jgroups-4,Test-NodeI-48950:[]) [CommandAwareRpcDispatcher] Got acceptable response: Responses{ > Test-NodeK-2872: value=SuccessfulResponse{responseValue=ImmortalCacheValue {value=B}} , received=true, suspected=false > 17:12:07,226 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.conflict.impl.OperationsDuringMergeConflictTest.testPartitionMergePolicy > java.lang.AssertionError: Key=MagicKey{13A4/DDFB0E77/56@Test-NodeI-48950}, Value=A, Cache Index=0, Topology=CacheTopology{id=20, rebalanceId=7, currentCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (2)[Test-NodeK-2872: 134+122, Test-NodeL-23686: 122+134]}, pendingCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (4)[Test-NodeK-2872: 134+122, Test-NodeL-23686: 122+134, Test-NodeI-48950: 0+256, Test-NodeJ-6577: 0+256]}, unionCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (4)[Test-NodeK-2872: 134+122, Test-NodeL-23686: 122+134, Test-NodeI-48950: 0+256, Test-NodeJ-6577: 0+256]}, phase=CONFLICT_RESOLUTION, actualMembers=[Test-NodeK-2872, Test-NodeL-23686, Test-NodeI-48950, Test-NodeJ-6577], persistentUUIDs=[40b58191-37f1-4fa4-8e4b-f1a7c17bfa59, 208d742d-ecc9-4792-9dd5-f74d5666f5a2, d8914096-a5a4-4e1e-95a0-27c50fee9999, 7464e58b-5e23-4c1b-909e-4e53055f12ca]} expected:<A> but was:<B> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.8.8.jar:?] > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) ~[testng-6.8.8.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) ~[testng-6.8.8.jar:?] > at org.infinispan.conflict.impl.BaseMergePolicyTest.assertCacheGet(BaseMergePolicyTest.java:160) ~[test-classes/:?] > at org.infinispan.conflict.impl.OperationsDuringMergeConflictTest.performMerge(OperationsDuringMergeConflictTest.java:121) ~[test-classes/:?] > at org.infinispan.conflict.impl.BaseMergePolicyTest.testPartitionMergePolicy(BaseMergePolicyTest.java:116) ~[test-classes/:?] > {noformat} > https://ci.infinispan.org/job/Infinispan/job/master/543/testReport/org.in... > Maybe we should use the union CH for reading during conflict resolution instead? > Speaking of which, {{PreferAvailabilityStrategy}} sets the {{unionCH}} field in the conflict resolution {{CacheTopology}}, but it is ignored because {{CacheTopologyControlCommand}} doesn't have a field for it. We should set {{unionCH=null}} in {{PreferAvailabilityStrategy}} to make things clearer. We should also try to reduce the number of times we log the cache topology during conflict resolution (even if it's only at trace level). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9009) Add test interrupting conflict resolution

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9009?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9009: ------------------------------- Sprint: Sprint 9.3.0.Alpha1 > Add test interrupting conflict resolution > ----------------------------------------- > > Key: ISPN-9009 > URL: https://issues.jboss.org/browse/ISPN-9009 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Ryan Emerson > Fix For: 9.3.0.Alpha1 > > > We need a test that starts conflict resolution and then crashes a node or starts another merge, to verify that conflict resolution is properly interrupted or restarted as necessary. > {{HotRodMergeTest}} was unintentionally testing this by starting the 2nd test before the 1st test's merge finished in all the server caches, but we need something more deterministic in core. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2018