[JBoss JIRA] (ISPN-10863) java.lang.IllegalAccessException logged by PropertyFormatter
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10863?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10863:
-----------------------------------
Fix Version/s: 10.1.0.CR1
(was: 10.1.0.Beta1)
> java.lang.IllegalAccessException logged by PropertyFormatter
> -------------------------------------------------------------
>
> Key: ISPN-10863
> URL: https://issues.jboss.org/browse/ISPN-10863
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 10.0.0.Final
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.1.0.CR1, 10.0.2.Final
>
>
> This is a benign issue being logged by AccessibleObject when PropertyFormatter attempts to accesses via reflection some config methods that are not accessible. JmxStatsFunctionalTest is one good example, and it's not failing because of this.
> {code}
> java.lang.IllegalAccessException: class org.infinispan.configuration.format.PropertyFormatter cannot access a member of class org.infinispan.configuration.cache.AuthorizationConfiguration with modifiers "static final"
> at java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at org.infinispan.configuration.format.PropertyFormatter.reflect(PropertyFormatter.java:101)
> at org.infinispan.configuration.format.PropertyFormatter.reflect(PropertyFormatter.java:110)
> at org.infinispan.configuration.format.PropertyFormatter.reflect(PropertyFormatter.java:101)
> at org.infinispan.configuration.format.PropertyFormatter.reflect(PropertyFormatter.java:101)
> at org.infinispan.configuration.format.PropertyFormatter.format(PropertyFormatter.java:131)
> at org.infinispan.cache.impl.AbstractDelegatingCache.getConfigurationAsProperties(AbstractDelegatingCache.java:616)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.infinispan.jmx.ResourceDMBean$InvokableSetterBasedMBeanAttributeInfo.invoke(ResourceDMBean.java:378)
> at org.infinispan.jmx.ResourceDMBean.getNamedAttribute(ResourceDMBean.java:289)
> at org.infinispan.jmx.ResourceDMBean.getAttribute(ResourceDMBean.java:172)
> at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:641)
> at java.management/com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678)
> at org.infinispan.jmx.JmxStatsFunctionalTest.testConfigurationProperties(JmxStatsFunctionalTest.java:307)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-10887) GlobalJmxStatisticsConfiguration.allowDuplicateDomains is not implemented atomically and can fail frequently
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10887?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10887:
-----------------------------------
Fix Version/s: 10.1.0.CR1
(was: 10.1.0.Beta1)
> GlobalJmxStatisticsConfiguration.allowDuplicateDomains is not implemented atomically and can fail frequently
> ------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-10887
> URL: https://issues.jboss.org/browse/ISPN-10887
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 10.0.0.Final
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.1.0.CR1, 10.0.2.Final
>
>
> The feature is supposed to allow detection of an already occupied jmx domain and generate a new unique one by adding an increasing number suffix. The implementation polls the MBeanServer registry using queryNames until a free domain is found. The unique domain generation and the registration of the first MBean to occupy it is not atomic, so multiple CacheManagers starting up concurrently can mistakenly pick up the same domain.
> This can be fixed by making it atomic, by not using queryNames and instead directly registering the first bean, retrying if InstanceAlreadyExistsException. The first bean has to be picked identically by all cache managers. We'll pick first the cache manager itself and register the other components afterwards.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-10906) JGroupsTransport instance is reused in tests
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10906?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10906:
-----------------------------------
Fix Version/s: 10.1.0.CR1
(was: 10.1.0.Beta1)
> JGroupsTransport instance is reused in tests
> --------------------------------------------
>
> Key: ISPN-10906
> URL: https://issues.jboss.org/browse/ISPN-10906
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.1.0.CR1
>
>
> The {{TRANSPORT}} {{AttributeDefinition}} uses {{IdentityAttributeCopier}}, which means that when a test uses {{GlobalConfigurationBuilder.read()}} to make a clone of the global configuration it keeps using the same {{JGroupsTransport}} instance. Both cache managers sort of work, but usually not as intended.
> We should detect when {{JGroupsTransport}}'s dependencies are injected twice and throw an exception. We should also consider changing the {{TRANSPORT}} copier to {{SimpleInstanceAttributeCopier}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-10910) Server should not keep running after a startup error
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10910?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10910:
-----------------------------------
Fix Version/s: 10.1.0.CR1
(was: 10.1.0.Beta1)
> Server should not keep running after a startup error
> ----------------------------------------------------
>
> Key: ISPN-10910
> URL: https://issues.jboss.org/browse/ISPN-10910
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.1.Final
> Reporter: Dan Berindei
> Priority: Major
> Fix For: 10.1.0.CR1
>
>
> Some startup exceptions are logged on the console and ignored:
> {noformat}
> java.lang.IllegalArgumentException: A metric with metricID MetricID{name='Server_Transport_numberOfGlobalConnections', tags=[_domain="test_domain",name="Memcached-11221"]} already exists
> java.lang.RuntimeException: java.lang.IllegalArgumentException: A metric with metricID MetricID{name='Server_Transport_numberOfGlobalConnections', tags=[_domain="test_domain",name="Memcached-11221"]} already exists
> at org.infinispan.server.core.AbstractProtocolServer.registerServerMBeans(AbstractProtocolServer.java:168)
> at org.infinispan.server.core.AbstractProtocolServer.startTransport(AbstractProtocolServer.java:116)
> at org.infinispan.server.core.AbstractProtocolServer.startInternal(AbstractProtocolServer.java:72)
> at org.infinispan.server.memcached.MemcachedServer.startInternal(MemcachedServer.java:60)
> at org.infinispan.server.memcached.MemcachedServer.startInternal(MemcachedServer.java:33)
> at org.infinispan.server.core.AbstractProtocolServer.start(AbstractProtocolServer.java:103)
> at org.infinispan.server.SecurityActions.lambda$startProtocolServer$4(SecurityActions.java:72)
> at org.infinispan.security.Security.doPrivileged(Security.java:47)
> at org.infinispan.server.SecurityActions.doPrivileged(SecurityActions.java:32)
> at org.infinispan.server.SecurityActions.startProtocolServer(SecurityActions.java:75)
> at org.infinispan.server.Server.lambda$run$1(Server.java:294)
> at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1654)
> at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
> at java.base/java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)
> at java.base/java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:746)
> at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
> at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
> at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
> at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
> at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:177)
> Caused by: java.lang.IllegalArgumentException: A metric with metricID MetricID{name='Server_Transport_numberOfGlobalConnections', tags=[_domain="test_domain",name="Memcached-11221"]} already exists
> at io.smallrye.metrics.MetricsRegistryImpl.register(MetricsRegistryImpl.java:129)
> at org.infinispan.metrics.impl.ApplicationMetricsRegistry.register(ApplicationMetricsRegistry.java:81)
> at org.infinispan.jmx.AbstractJmxRegistration.registerExternalMBean(AbstractJmxRegistration.java:222)
> at org.infinispan.jmx.CacheManagerJmxRegistration.registerExternalMBean(CacheManagerJmxRegistration.java:16)
> at org.infinispan.server.core.AbstractProtocolServer.registerServerMBeans(AbstractProtocolServer.java:165)
> ... 20 more
> {noformat}
> Other exceptions are only logged during stop:
> {noformat}
> 09:09:48,404 ERROR (testng-ShutdownRestIT:[]) [TestSuiteProgress] Test failed: suite.null
> java.lang.RuntimeException: null
> at org.infinispan.server.test.EmbeddedInfinispanServerDriver.stop(EmbeddedInfinispanServerDriver.java:59) ~[test-classes/:?]
> at org.infinispan.server.test.InfinispanServerDriver.after(InfinispanServerDriver.java:101) ~[test-classes/:?]
> at org.infinispan.server.test.InfinispanServerRule$1.evaluate(InfinispanServerRule.java:72) ~[test-classes/:?]
> at org.junit.rules.RunRules.evaluate(RunRules.java:20) ~[junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12]
> at org.junit.runners.Suite.runChild(Suite.java:128) [junit-4.12.jar:4.12]
> at org.junit.runners.Suite.runChild(Suite.java:27) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12]
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384) [surefire-booter-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345) [surefire-booter-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126) [surefire-booter-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418) [surefire-booter-3.0.0-M3.jar:3.0.0-M3]
> Suppressed: java.util.concurrent.ExecutionException: io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Address already in use
> at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395) ~[?:?]
> at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999) ~[?:?]
> at org.infinispan.server.test.EmbeddedInfinispanServerDriver.stop(EmbeddedInfinispanServerDriver.java:65) ~[test-classes/:?]
> at org.infinispan.server.test.InfinispanServerDriver.after(InfinispanServerDriver.java:101) ~[test-classes/:?]
> at org.infinispan.server.test.InfinispanServerRule$1.evaluate(InfinispanServerRule.java:72) ~[test-classes/:?]
> at org.junit.rules.RunRules.evaluate(RunRules.java:20) ~[junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12]
> at org.junit.runners.Suite.runChild(Suite.java:128) [junit-4.12.jar:4.12]
> at org.junit.runners.Suite.runChild(Suite.java:27) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) [junit-4.12.jar:4.12]
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12]
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) [surefire-junit47-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384) [surefire-booter-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345) [surefire-booter-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126) [surefire-booter-3.0.0-M3.jar:3.0.0-M3]
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418) [surefire-booter-3.0.0-M3.jar:3.0.0-M3]
> Caused by: io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Address already in use
> {noformat}
> It would be much better for the test suite if the server failed fast instead of showing an exception only after the test has run with a broken server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-10939) PessimisticTxPartitionAndMergeDuringRollbackTest random failures
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10939?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10939:
-----------------------------------
Fix Version/s: 10.1.0.CR1
(was: 10.1.0.Beta1)
> PessimisticTxPartitionAndMergeDuringRollbackTest random failures
> ----------------------------------------------------------------
>
> Key: ISPN-10939
> URL: https://issues.jboss.org/browse/ISPN-10939
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 10.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.1.0.CR1
>
> Attachments: test.log.gz
>
>
> {{PessimisticTxPartitionAndMergeDuringRollbackTest.testPrimaryOwnerIsolatedPartitionWithDiscard[DIST_SYNC, DENY_READ_WRITES]}} sometimes fails because {{NodeC}} never rolls back {{NodeA}}'s transaction. It's normal to not roll back the transaction on {{NodeC}} while it's in {{DEGRADED_MODE}}, but it should roll back the transaction after the merge.
> {noformat}
> 16:31:28,895 TRACE (ForkThread-1,PessimisticTxPartitionAndMergeDuringRollbackTest:[]) [TransactionCoordinator] rollback transaction GlobalTx:Test-NodeA-24422:22
> 16:31:28,897 DEBUG (jgroups-7,Test-NodeC-35037:[]) [BaseTxPartitionAndMergeTest] Ignoring command RollbackCommand {gtx=GlobalTx:Test-NodeA-24422:22, cacheName='pes-cache', topologyId=13}
> 16:31:28,898 DEBUG (testng-Test:[]) [GMS] Test-NodeC-35037: installing view [Test-NodeC-35037|31] (1) [Test-NodeC-35037]
> 16:31:28,904 DEBUG (testng-Test:[]) [GMS] Test-NodeA-24422: installing view [Test-NodeA-24422|32] (3) [Test-NodeA-24422, Test-NodeB-15428, Test-NodeD-40706]
> 16:31:28,968 TRACE (transport-thread-Test-NodeC-p181-t1:[Topology-pes-cache]) [TransactionTable] Checking for transactions originated on leavers. Current cache members are [Test-NodeC-35037], remote transactions: 1
> 16:31:28,971 TRACE (transport-thread-Test-NodeC-p181-t1:[Topology-pes-cache]) [TransactionTable] Checking transaction GlobalTx:Test-NodeA-24422:22
> 16:31:28,971 TRACE (transport-thread-Test-NodeC-p181-t1:[Topology-pes-cache]) [PartitionHandlingManagerImpl] Can rollback transaction? false
> 16:31:29,113 DEBUG (testng-Test:[]) [GMS] Test-NodeC-35037: installing view MergeView::[Test-NodeC-35037|35] (4) [Test-NodeC-35037, Test-NodeA-24422, Test-NodeB-15428, Test-NodeD-40706], 2 subgroups: [Test-NodeC-35037|33] (1) [Test-NodeC-35037], [Test-NodeA-24422|34] (3) [Test-NodeA-24422, Test-NodeB-15428, Test-NodeD-40706]
> 16:31:29,291 TRACE (transport-thread-Test-NodeC-p181-t4:[Topology-pes-cache]) [TransactionTable] Checking transaction GlobalTx:Test-NodeA-24422:22
> 16:31:29,291 TRACE (transport-thread-Test-NodeC-p181-t4:[Topology-pes-cache]) [TransactionTable] No remote transactions pertain to originator(s) who have left the cluster.
> 16:31:29,435 DEBUG (testng-Test:[]) [PessimisticTxPartitionAndMergeDuringRollbackTest] Cluster merged
> 16:31:29,436 TRACE (testng-Test:[]) [PessimisticTxPartitionAndMergeDuringRollbackTest] Local tx=[], remote tx=[GlobalTx:Test-NodeA-24422:22], for cache Test-NodeC-35037
> ...
> 16:31:39,446 TRACE (testng-Test:[]) [PessimisticTxPartitionAndMergeDuringRollbackTest] Local tx=[], remote tx=[GlobalTx:Test-NodeA-24422:22], for cache Test-NodeC-35037
> 16:31:39,446 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.partitionhandling.PessimisticTxPartitionAndMergeDuringRollbackTest.testPrimaryOwnerIsolatedPartitionWithDiscard[DIST_SYNC, DENY_READ_WRITES]
> java.lang.AssertionError: There are pending transactions!
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.14.3.jar:?]
> at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) ~[testng-6.14.3.jar:?]
> at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:250) ~[test-classes/:?]
> at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:390) ~[test-classes/:?]
> at org.infinispan.test.MultipleCacheManagersTest.assertNoTransactions(MultipleCacheManagersTest.java:947) ~[test-classes/:?]
> at org.infinispan.partitionhandling.BaseTxPartitionAndMergeTest.finalAsserts(BaseTxPartitionAndMergeTest.java:101) ~[test-classes/:?]
> at org.infinispan.partitionhandling.BasePessimisticTxPartitionAndMergeTest.doTest(BasePessimisticTxPartitionAndMergeTest.java:83) ~[test-classes/:?]
> at org.infinispan.partitionhandling.PessimisticTxPartitionAndMergeDuringRollbackTest.testPrimaryOwnerIsolatedPartitionWithDiscard(PessimisticTxPartitionAndMergeDuringRollbackTest.java:43) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-10930) MassIndexer does not reindex cache with OFF_HEAP and protobuf storage
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10930?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10930:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> MassIndexer does not reindex cache with OFF_HEAP and protobuf storage
> ---------------------------------------------------------------------
>
> Key: ISPN-10930
> URL: https://issues.jboss.org/browse/ISPN-10930
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 9.4.16.Final, 10.0.1.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 10.1.0.Beta1
>
>
> The MassIndexer iterates though the data and creates indexing jobs, and in order to a protobuf payload to be reinidex, it needs to be a ProtobufValueWrapper. When using OFF_HEAP, the data container stores values as WrappedBytes and they are ingored when indexing
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month