May 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5461) FileDescriptorSource.fromResources and FileDescriptorSource.addProtoFiles should have a ClassLoader argument

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5461?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5461: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > FileDescriptorSource.fromResources and FileDescriptorSource.addProtoFiles should have a ClassLoader argument > ------------------------------------------------------------------------------------------------------------ > > Key: ISPN-5461 > URL: https://issues.jboss.org/browse/ISPN-5461 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Affects Versions: 7.2.1.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.2.Final, 8.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5481) ConfigurationOverrideTest random failures

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5481: ---------------------------------- Summary: ConfigurationOverrideTest random failures Key: ISPN-5481 URL: https://issues.jboss.org/browse/ISPN-5481 Project: Infinispan Issue Type: Bug Components: Core, Test Suite - Core Affects Versions: 7.2.1.Final Reporter: Dan Berindei Priority: Critical Fix For: 8.0.0.Alpha1 {{ConfigurationOverrideTest}} uses the default global configuration, and it fails when another test has already registered a cache manager MBean in JMX with the same name: {noformat} org.infinispan.jmx.JmxDomainConflictException: ISPN000034: There's already a JMX MBean instance type=CacheManager,name="DefaultCacheManager" already registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:51) at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79) at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73) at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37) at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41) at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:625) at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:218) at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:199) at org.infinispan.configuration.ConfigurationOverrideTest.testOverrideWithStore(ConfigurationOverrideTest.java:80) {noformat} We should verify the other tests as well, to make sure they all use the {{PerThreadMBeanServerLookup}} and/or a unique JMX domain. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5322) Support replicated cache for PH in a read-only mode

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5322?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5322: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.2.2.Final 8.0.0.Alpha1 Resolution: Done Removed warning that stated that replication cache didn't support partition handling. > Support replicated cache for PH in a read-only mode > --------------------------------------------------- > > Key: ISPN-5322 > URL: https://issues.jboss.org/browse/ISPN-5322 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Wolf-Dieter Fink > Labels: partition_handling > Fix For: 7.2.2.Final, 8.0.0.Alpha1 > > > Current a REPL cache can not enable partition handling. > There is a WARN message that the PH is ignored for replicated mode. > The reason is that if one node leave the cache can become inconsistent. > But for some reason it might be worth to have the cache available as read-only, so there is no way to make the cache inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5323) Add a configuration option for partition handling to force DEGRADED mode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5323?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-5323: ------------------------------------ I'm not sure the configuration is the write place for this, and we already have a JMX operation to force DEGRADED mode. If we did introduce such a configuration setting, it would mean that the cluster enters READONLY mode every time one of the nodes crashes, regardless of {{numOwners}}, and the only way to make the cluster AVAILABLE again would be via administrator intervention. I doubt that would be very useful... > Add a configuration option for partition handling to force DEGRADED mode > ------------------------------------------------------------------------ > > Key: ISPN-5323 > URL: https://issues.jboss.org/browse/ISPN-5323 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Wolf-Dieter Fink > Labels: partition_handling > > Current one part of the partition can be stay AVAILABLE and therefor it is not possible to read key's in a DEGRADED partition as it might be stale. > But for some reason it might be worth to be able to read such keys. > In that case it must be ensured that no partition enter AVAILABLE mode and rebalance. > An additional configuration migt force DEGRADED mode for all partitions, in this case it will be possible to have read access to all keys where this part. does not have all owners AND have full access if all owners are available. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5322) Support replicated cache for PH in a read-only mode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5322?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5322: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3479 Indeed [~william.burns], partition handling will work with replicated caches. Just like in distributed mode, there is no read-only mode, only degraded mode. A cache partition enters degraded mode if the current set of members does not contain a simple majority of the members in the latest stable cache topology, and the stable cache topology is updated when there is no pending rebalance. When a node joins, that means after the joiner receives the state, when a node leaves, it means after all the owners confirm the new topology. > Support replicated cache for PH in a read-only mode > --------------------------------------------------- > > Key: ISPN-5322 > URL: https://issues.jboss.org/browse/ISPN-5322 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Wolf-Dieter Fink > Labels: partition_handling > > Current a REPL cache can not enable partition handling. > There is a WARN message that the PH is ignored for replicated mode. > The reason is that if one node leave the cache can become inconsistent. > But for some reason it might be worth to have the cache available as read-only, so there is no way to make the cache inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5322) Support replicated cache for PH in a read-only mode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5322?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5322: ------------------------------- Status: Open (was: New) > Support replicated cache for PH in a read-only mode > --------------------------------------------------- > > Key: ISPN-5322 > URL: https://issues.jboss.org/browse/ISPN-5322 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Wolf-Dieter Fink > Labels: partition_handling > > Current a REPL cache can not enable partition handling. > There is a WARN message that the PH is ignored for replicated mode. > The reason is that if one node leave the cache can become inconsistent. > But for some reason it might be worth to have the cache available as read-only, so there is no way to make the cache inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5474) Transactions created when applying state should never be replicated

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5474?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5474: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Transactions created when applying state should never be replicated > ------------------------------------------------------------------- > > Key: ISPN-5474 > URL: https://issues.jboss.org/browse/ISPN-5474 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 7.2.2.Final, 8.0.0.Alpha1 > > > {{BaseRpcInterceptor.shouldInvokeRemoteTxCommand}} forces the replication of transactional commands if the topology id changed since the start of the transaction. However, this can also apply for transaction used internally to apply state during state transfer. > For a state transfer tx, the collection of affected keys is empty, but {{ReplicationLogic.getOwners(Collection)}} returns {{null}} instead of {{Collections.emptySet()}}, and the prepare/commit command ends up being replicated to all the other nodes. > The extra RPC sometimes causes failures in {{ReplCommandRetryTest}}. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5322) Support replicated cache for PH in a read-only mode

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5322?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-5322: ------------------------------------- Partition handling appears to be supported for replication caches as of ISPN-4574. However the warn message is still present. So it seems for this JIRA we just need to remove the warning message to not cause confusion for users when enabling replication partition handling. [~dan.berindei] can you confirm? > Support replicated cache for PH in a read-only mode > --------------------------------------------------- > > Key: ISPN-5322 > URL: https://issues.jboss.org/browse/ISPN-5322 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Wolf-Dieter Fink > Labels: partition_handling > > Current a REPL cache can not enable partition handling. > There is a WARN message that the PH is ignored for replicated mode. > The reason is that if one node leave the cache can become inconsistent. > But for some reason it might be worth to have the cache available as read-only, so there is no way to make the cache inconsistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5314) EventSocketTimeoutTest.testSocketTimeoutWithEvent randomly failing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5314?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5314: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1222860 > EventSocketTimeoutTest.testSocketTimeoutWithEvent randomly failing > ------------------------------------------------------------------ > > Key: ISPN-5314 > URL: https://issues.jboss.org/browse/ISPN-5314 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 7.2.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.2.0.CR1 > > Attachments: infinispan.log > > > {code} > org.infinispan.client.hotrod.exceptions.TransportException:: java.net.SocketTimeoutException > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:184) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:282) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:94) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) > at org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:50) > at org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:30) > at org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:19) > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:52) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:237) > at org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:79) > at org.infinispan.client.hotrod.event.EventSocketTimeoutTest$1.call(EventSocketTimeoutTest.java:60) > at org.infinispan.client.hotrod.test.HotRodClientTestingUtil.withClientListener(HotRodClientTestingUtil.java:145) > at org.infinispan.client.hotrod.event.EventSocketTimeoutTest.testSocketTimeoutWithEvent(EventSocketTimeoutTest.java:47) > 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:84) > 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:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > 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) > Caused by: java.net.SocketTimeoutException > at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:229) > at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) > at java.io.BufferedInputStream.read(BufferedInputStream.java:254) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:179) > ... 32 more > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5478) Add readOnly test for MapStressTest

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5478?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5478: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add readOnly test for MapStressTest > ----------------------------------- > > Key: ISPN-5478 > URL: https://issues.jboss.org/browse/ISPN-5478 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Alpha1, 8.0.0.Final > > > We have a lot of read/write & read/write/remove tests in the MapStressTest. We should add something for read only. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2015