[JBoss JIRA] (ISPN-4891) ExpiryTest failures caused by ISPN-4836
by Pedro Ruivo (JIRA)
Pedro Ruivo created ISPN-4891:
---------------------------------
Summary: ExpiryTest failures caused by ISPN-4836
Key: ISPN-4891
URL: https://issues.jboss.org/browse/ISPN-4891
Project: Infinispan
Issue Type: Bug
Reporter: Pedro Ruivo
Assignee: William Burns
Fix For: 7.0.0.Final
The following tests are failing:
{code}
ExpiryTest.testEntrySetAfterExpiryInPut:233->doTestEntrySetAfterExpiryInPut:283 expected:<[1=v1-testEntrySetAfterExpiryInPut, 2=v2-testEntrySetAfterExpiryInPut]> but was:<[]>
ExpiryTest.testKeySetAfterExpiryInTransaction:370->doKeySetAfterExpiryInTransaction:402 expected:<[1, 2, 3]> but was:<[3]>
{code}
A possible solution (by Dan) would be to copy to make sure the entries don't disappear from the set.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4890) Entry iterator should throw AvailabilityException in degraded mode
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4890?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4890:
-------------------------------
Status: Open (was: New)
> Entry iterator should throw AvailabilityException in degraded mode
> ------------------------------------------------------------------
>
> Key: ISPN-4890
> URL: https://issues.jboss.org/browse/ISPN-4890
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core
> Affects Versions: 7.0.0.CR2
> Reporter: Dan Berindei
> Assignee: William Burns
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 7.0.0.Final
>
>
> When the distributed entry iterator gets a suspect exception, it assumes that the CH will be soon updated to remove the leaver, and retries to contact the primary owner of the segment.
> But if the cache is in degraded mode, the consistent hash is no longer updated, and the entry iterator enters an infinite loop.
> {noformat}
> 11:58:35,622 TRACE (testng-DelayedAvailabilityUpdateTest:) [DistributedEntryRetriever] Request to NodeC-51013=[50, 51, 20, 52, 21, 53, 22, 54, 23, 24, 25, 26, 27, 28, 29] for cd886604-960b-431a-81a0-efbb51eed57f was suspect, must resend to a new node!
> 11:58:35,622 TRACE (testng-DelayedAvailabilityUpdateTest:) [DistributedEntryRetriever] Request to NodeC-51013=[50, 51, 20, 52, 21, 53, 22, 54, 23, 24, 25, 26, 27, 28, 29] for cd886604-960b-431a-81a0-efbb51eed57f was suspect, must resend to a new node!
> 11:58:35,622 TRACE (testng-DelayedAvailabilityUpdateTest:) [DistributedEntryRetriever] Request to NodeC-51013=[50, 51, 20, 52, 21, 53, 22, 54, 23, 24, 25, 26, 27, 28, 29] for cd886604-960b-431a-81a0-efbb51eed57f was suspect, must resend to a new node!
> ...
> {noformat}
> This is visible when running the partition handling tests (e.g. DelayedAvailabilityUpdateTest) with trace logging enabled, as {{TestingUtil.killCaches()}} logs the cache contents at trace level. As an aside, {{TestingUtil.killCaches()}} should probably use {{Flag.CACHE_MODE_LOCAL}} to print only the entries on each node.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4847) Improve indexing performance
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-4847?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on ISPN-4847:
---------------------------------------
Right, I only mentioned HSEARCH-1681 so that if you have (write) benchmark tests which include the optimise(), keep in mind that some work isn't being done at index storage level.. so it might show an unfair result.
> Improve indexing performance
> ----------------------------
>
> Key: ISPN-4847
> URL: https://issues.jboss.org/browse/ISPN-4847
> Project: Infinispan
> Issue Type: Enhancement
> Components: Embedded Querying, Lucene Directory
> Affects Versions: 7.0.0.CR1
> Reporter: Radim Vansa
> Assignee: Sanne Grinovero
> Priority: Critical
>
> This JIRA is focused on optimizing performance of use case where the application uses short or none transactions - therefore, no batching can be applied - and then performs the query and expects that the result will be consistent (please, specify in documentation if any lag after cache.put() or tx.commit() is required and if the application can detect that the update has been applied).
> We are well aware (see BZ) that indexing can be implemented with very low overhead, but the throughput is thousands of times lower [1] (configuration in [2]) with distributed mode storing index in replicated cache, and about 4x slowdown when comparing replicated cache without indexing and indexing to NRT FS/RAM.
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-query-index...
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-query-index...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4890) Entry iterator should throw AvailabilityException in degraded mode
by Dan Berindei (JIRA)
Dan Berindei created ISPN-4890:
----------------------------------
Summary: Entry iterator should throw AvailabilityException in degraded mode
Key: ISPN-4890
URL: https://issues.jboss.org/browse/ISPN-4890
Project: Infinispan
Issue Type: Bug
Components: Core, Test Suite - Core
Affects Versions: 7.0.0.CR2
Reporter: Dan Berindei
Assignee: William Burns
Priority: Blocker
Fix For: 7.0.0.Final
When the distributed entry iterator gets a suspect exception, it assumes that the CH will be soon updated to remove the leaver, and retries to contact the primary owner of the segment.
But if the cache is in degraded mode, the consistent hash is no longer updated, and the entry iterator enters an infinite loop.
{noformat}
11:58:35,622 TRACE (testng-DelayedAvailabilityUpdateTest:) [DistributedEntryRetriever] Request to NodeC-51013=[50, 51, 20, 52, 21, 53, 22, 54, 23, 24, 25, 26, 27, 28, 29] for cd886604-960b-431a-81a0-efbb51eed57f was suspect, must resend to a new node!
11:58:35,622 TRACE (testng-DelayedAvailabilityUpdateTest:) [DistributedEntryRetriever] Request to NodeC-51013=[50, 51, 20, 52, 21, 53, 22, 54, 23, 24, 25, 26, 27, 28, 29] for cd886604-960b-431a-81a0-efbb51eed57f was suspect, must resend to a new node!
11:58:35,622 TRACE (testng-DelayedAvailabilityUpdateTest:) [DistributedEntryRetriever] Request to NodeC-51013=[50, 51, 20, 52, 21, 53, 22, 54, 23, 24, 25, 26, 27, 28, 29] for cd886604-960b-431a-81a0-efbb51eed57f was suspect, must resend to a new node!
...
{noformat}
This is visible when running the partition handling tests (e.g. DelayedAvailabilityUpdateTest) with trace logging enabled, as {{TestingUtil.killCaches()}} logs the cache contents at trace level. As an aside, {{TestingUtil.killCaches()}} should probably use {{Flag.CACHE_MODE_LOCAL}} to print only the entries on each node.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4847) Improve indexing performance
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-4847?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-4847:
-----------------------------------------
HSEARCH-1681 seems unrelated to performance improvement as optimized is not commonly used and the benefit is felt at query (not index) time
> Improve indexing performance
> ----------------------------
>
> Key: ISPN-4847
> URL: https://issues.jboss.org/browse/ISPN-4847
> Project: Infinispan
> Issue Type: Enhancement
> Components: Embedded Querying, Lucene Directory
> Affects Versions: 7.0.0.CR1
> Reporter: Radim Vansa
> Assignee: Sanne Grinovero
> Priority: Critical
>
> This JIRA is focused on optimizing performance of use case where the application uses short or none transactions - therefore, no batching can be applied - and then performs the query and expects that the result will be consistent (please, specify in documentation if any lag after cache.put() or tx.commit() is required and if the application can detect that the update has been applied).
> We are well aware (see BZ) that indexing can be implemented with very low overhead, but the throughput is thousands of times lower [1] (configuration in [2]) with distributed mode storing index in replicated cache, and about 4x slowdown when comparing replicated cache without indexing and indexing to NRT FS/RAM.
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-query-index...
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-query-index...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4783) Using new ArrayList<>(resultCache.values())
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4783?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-4783:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Using new ArrayList<>(resultCache.values())
> -------------------------------------------
>
> Key: ISPN-4783
> URL: https://issues.jboss.org/browse/ISPN-4783
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 6.0.2.Final, 7.0.0.CR2
> Reporter: Markus Vogt
> Assignee: William Burns
> Fix For: 7.0.0.Final
>
> Attachments: cacheConfig.xml, ISPN4783_Test.java
>
>
> Hi,
> I am a little bit confused about the behaviour of getting the values from a cache and inserting into an ArrayList.
> I've putted one value into a cache, so that cache.size() is returning 1. If i now use 'new ArrayList<>(resultCache.values())', there will be two items in the list.
> By iterating over the cache, only one iteration will run... Where comes the second item from?
> Regards,
> Markus
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4878) StateTransferSuppressIT always fails: the protobuf metadata cache can't start with state transfer suspended
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4878?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-4878:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> StateTransferSuppressIT always fails: the protobuf metadata cache can't start with state transfer suspended
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-4878
> URL: https://issues.jboss.org/browse/ISPN-4878
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 7.0.0.CR2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 7.0.0.Final
>
>
> {noformat}
> 2014-10-24 09:50:05,525 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.infinispan.clustered.memcachedCache: org.jboss.msc.service.StartException in service jboss.infinispan.clustered.memcachedCache: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_20]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_20]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20]
> Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.InterruptedException on object of type StateTransferManagerImpl
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:171)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:216)
> at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:764)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:584)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:539)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:416)
> at org.infinispan.query.remote.ProtobufMetadataManager.getCache(ProtobufMetadataManager.java:91)
> at org.infinispan.query.remote.LifecycleManager.cacheStarting(LifecycleManager.java:102)
> at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:228)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:214)
> at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:764)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:584)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:539)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:416)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:430)
> at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:89)
> at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:80)
> at org.infinispan.server.infinispan.SecurityActions$4.run(SecurityActions.java:116)
> at org.infinispan.server.infinispan.SecurityActions$4.run(SecurityActions.java:113)
> at org.infinispan.security.Security.doPrivileged(Security.java:76)
> at org.infinispan.server.infinispan.SecurityActions.doPrivileged(SecurityActions.java:60)
> at org.infinispan.server.infinispan.SecurityActions.startCache(SecurityActions.java:121)
> at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:79)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] ... 3 more
> Caused by: org.infinispan.commons.CacheException: Initial state transfer timed out for cache ___protobuf_metadata on node2/clustered
> at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:216)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_20]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_20]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_20]
> at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0_20]
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168) ... 31 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4868) Release.py script fails to copy artifacts
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4868?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-4868:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Release.py script fails to copy artifacts
> -----------------------------------------
>
> Key: ISPN-4868
> URL: https://issues.jboss.org/browse/ISPN-4868
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.0.CR1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Blocker
> Fix For: 7.0.0.Final
>
>
> {code}
> [INFO] Step 8: Complete
> [INFO] Copying from /mnt/ebs/release/infinispan/as-modules/client/target/distribution to 7.0.0.CR2
> [INFO] Copying from /mnt/ebs/release/infinispan/distribution/target/distribution to 7.0.0.CR2
> Process Process-3:
> Traceback (most recent call last):
> File "/usr/lib64/python2.6/multiprocessing/process.py", line 232, in _bootstrap
> [INFO] Copying from /mnt/ebs/release/infinispan/as-modules/embedded/target/distribution to 7.0.0.CR2
> self.run()
> File "/usr/lib64/python2.6/multiprocessing/process.py", line 88, in run
> self._target(*self._args, **self._kwargs)
> File "bin/release.py", line 204, in upload_artifacts
> [INFO] Copying from /mnt/ebs/release/infinispan/server/integration/target/distribution to 7.0.0.CR2
> File "/usr/lib64/python2.6/shutil.py", line 95, in copy2
> copyfile(src, dst)
> File "/usr/lib64/python2.6/shutil.py", line 51, in copyfile
> with open(dst, 'wb') as fdst:
> IOError: [Errno 2] No such file or directory: '7.0.0.CR2'
> Process Process-2:
> Traceback (most recent call last):
> File "/usr/lib64/python2.6/multiprocessing/process.py", line 232, in _bootstrap
> self.run()
> File "/usr/lib64/python2.6/multiprocessing/process.py", line 88, in run
> self._target(*self._args, **self._kwargs)
> File "bin/release.py", line 204, in upload_artifacts
> File "/usr/lib64/python2.6/shutil.py", line 96, in copy2
> copystat(src, dst)
> File "/usr/lib64/python2.6/shutil.py", line 66, in copystat
> os.utime(dst, (st.st_atime, st.st_mtime))
> OSError: [Errno 2] No such file or directory: '7.0.0.CR2/infinispan-7.0.0.CR2-minimal.zip'
> Process Process-4:
> Traceback (most recent call last):
> File "/usr/lib64/python2.6/multiprocessing/process.py", line 232, in _bootstrap
> self.run()
> File "/usr/lib64/python2.6/multiprocessing/process.py", line 88, in run
> self._target(*self._args, **self._kwargs)
> File "bin/release.py", line 204, in upload_artifacts
> File "/usr/lib64/python2.6/shutil.py", line 96, in copy2
> copystat(src, dst)
> File "/usr/lib64/python2.6/shutil.py", line 66, in copystat
> os.utime(dst, (st.st_atime, st.st_mtime))
> OSError: [Errno 2] No such file or directory: '7.0.0.CR2/infinispan-as-embedded-modules-7.0.0.CR2.zip'
> {code}
> Only two artifacts are copied:
> infinispan-server-7.0.0.VERSION-bin.zip
> infinispan-server-7.0.0.VERSION-sources.zip
> Missing artifacts:
> infinispan-7.0.0.VERSION-all.zip
> infinispan-7.0.0.VERSION-bin.zip
> infinispan-7.0.0.VERSION-src.zip
> infinispan-as-client-modules-7.0.0.VERSION.zip
> infinispan-as-embedded-modules-7.0.0.VERSION.zip
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4865) Missing artifact sources during javadoc generation on distribution
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4865?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-4865:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Missing artifact sources during javadoc generation on distribution
> ------------------------------------------------------------------
>
> Key: ISPN-4865
> URL: https://issues.jboss.org/browse/ISPN-4865
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.0.CR1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 7.0.0.Final
>
>
> {{mvn clean install -Dmaven.test.skip.exec=true -Pdistribution -s maven-settings.xml}}
> Fails with:
> {code}
> [INFO] Infinispan Distribution ............................ FAILURE [ 31.539 s]
> [INFO] Infinispan ......................................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 46.833 s
> [INFO] Finished at: 2014-10-20T20:22:20+00:00
> [INFO] Final Memory: 73M/261M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.10:javadoc (javadoc) on project infinispan-distribution: An error has occurred in JavaDocs report generation: Failed to resolve one or more javadoc source/resource artifacts:
> [ERROR]
> [ERROR] Missing:
> [ERROR] ----------
> [ERROR] 1) antlr:antlr:jar:sources:2.7.7
> [ERROR]
> [ERROR] Try downloading the file manually from the project website.
> [ERROR]
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=antlr -DartifactId=antlr -Dversion=2.7.7 -Dclassifier=sources -Dpackaging=jar -Dfile=/path/to/file
> [ERROR]
> [ERROR] Alternatively, if you host your own repository you can deploy the file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=antlr -DartifactId=antlr -Dversion=2.7.7 -Dclassifier=sources -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> [ERROR]
> [ERROR] Path to dependency:
> [ERROR] 1) org.infinispan:infinispan-distribution:pom:7.0.0-SNAPSHOT
> [ERROR] 2) antlr:antlr:jar:sources:2.7.7
> [ERROR]
> [ERROR] ----------
> [ERROR] 1 required artifact is missing.
> [ERROR]
> [ERROR] for artifact:
> [ERROR] org.infinispan:infinispan-distribution:pom:7.0.0-SNAPSHOT
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] redhat-earlyaccess-repository-group (http://maven.repository.redhat.com/earlyaccess/all/, releases=true, snapshots=true),
> [ERROR] jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public-jboss/, releases=true, snapshots=true),
> [ERROR] jboss-public-repository (https://repository.jboss.org/nexus/content/groups/public, releases=true, snapshots=true),
> [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false)
> [ERROR] -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months