[infinispan-issues] [JBoss JIRA] Commented: (ISPN-937) FLUSH removal causing state transfer timeouts
Paul Ferraro (JIRA)
jira-events at lists.jboss.org
Fri Feb 25 00:18:29 EST 2011
[ https://issues.jboss.org/browse/ISPN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584652#comment-12584652 ]
Paul Ferraro commented on ISPN-937:
-----------------------------------
Here's the programmatic configuration of the cache triggering the attached timeout:
GlobalConfiguration global = GlobalConfiguration.getClusteredDefault();
global.setClusterName("testing");
global.setCacheManagerName("container" + containerIndex++);
global.setStrictPeerToPeer(false);
Configuration config = new Configuration();
config.setInvocationBatchingEnabled(true);
config.setIsolationLevel(IsolationLevel.REPEATABLE_READ);
config.setSyncReplTimeout(20000);
config.setLockAcquisitionTimeout(15000);
config.setCacheMode(CacheMode.REPL_SYNC);
config.setFetchInMemoryState(true);
config.setSyncCommitPhase(true);
config.setSyncRollbackPhase(true);
EmbeddedCacheManager container = new DefaultCacheManager(global, config, true);
> FLUSH removal causing state transfer timeouts
> ---------------------------------------------
>
> Key: ISPN-937
> URL: https://issues.jboss.org/browse/ISPN-937
> Project: Infinispan
> Issue Type: Bug
> Components: Cache Server
> Affects Versions: 4.2.1.CR2
> Reporter: Michal Linhard
> Assignee: Vladimir Blagojevic
> Fix For: 4.2.1.FINAL
>
> Attachments: hotrod-server-stdout.txt, hotrodconsole-0.0.1-SNAPSHOT-bin.zip, infinispan.xml, server1.log, server2-stdout.log, server2.log, test.log
>
>
> FLUSH removal (ISPN-83) is causing issues with state transfer as shown below. Vladimir, mind looking into it?
> ---------
> This is something that happend to me when playing with hotrod servers.
> I've built infinispan distribution from source (mvn install -P distribution -DskipTests=true)
> unzipped infinispan-4.2.1.CR2-all.zip 2x to folders
> distro1
> distro2
> created 2 virtual ifaces
> 192.168.11.101 test1
> 192.168.11.102 test2
> ran
> distro1/bin/startServer.sh -r hotrod -l test1 -c /home/mlinhard/dev/projects/infinispan/issues/infinispan.xml
> distro2/bin/startServer.sh -r hotrod -l test2 -c /home/mlinhard/dev/projects/infinispan/issues/infinispan.xml
> ran demo-hotrod-console
> hotrodconsole-0.0.1-SNAPSHOT/bin/console.sh test1
> entered
> >put a a (which means put value "a" under key "a")
> the servers waited a bit and then server 2 wrote some errors to stdout (I guess after some timeout expired)
> client was still blocked, after some time produced
> ERROR: Invalid magic number. Expected a1 and received 50
> attaching
> - binary version of demo-hotrod-console (source: https://github.com/mlinhard/demo-hotrod-console)
> - server 2 stdout
> - infinispan.xml
> I tried this with 4.2.1.CR1 and it worked.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list