Bug 758218

Summary: View installation failure in performance tests
Product: [JBoss] JBoss Data Grid 6 Reporter: Michal Linhard <misoli>
Component: InfinispanAssignee: Tristan Tarrant <ttarrant>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: jdg-bugs, mlinhard, msurtani
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-21 13:29:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michal Linhard 2011-11-29 15:03:34 UTC
In the client stress test we have view installation failures:
http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-PERF/job/edg-60-perf-client-stress-test-hotrod/110/

It's manifestation of
https://issues.jboss.org/browse/ISPN-1508 (which is marked as resolved)
that are connected to the way how hotrod server is started.

In this case the ERROR reported is not critical and the cluster can heal itself after a certain time.

However this cannot be considered a final solution (ERROR free startup)

Comment 1 Michal Linhard 2011-11-29 15:06:45 UTC
EDG build:
http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-build-edg-from-source/52/artifact/edg-srcbuild.zip

Infinispan version: 5.1.0.BETA5

Comment 2 Michal Linhard 2011-12-01 08:39:30 UTC
Well in certain tests the cluster can't heal itself:

https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-PERF/job/edg-60-perf-client-stress-test-hotrod/128

the cluster won't form in 4 minutes timeout in scenarios where I setup a special node startup delay pattern:

      host1:node01:delay 12000;
      host2:node02:delay 0;
      host3:node03:delay 3000;
      host4:node04:delay 6000;

Comment 3 Michal Linhard 2011-12-01 10:15:57 UTC
Raising severity. This is a blocker for EDG QE performance tests, currently no workaround seems to exist.