[infinispan-issues] [JBoss JIRA] (ISPN-1942) State transfer timeout confusion
Dan Berindei (JIRA)
jira-events at lists.jboss.org
Mon Mar 26 17:53:47 EDT 2012
[ https://issues.jboss.org/browse/ISPN-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679479#comment-12679479 ]
Dan Berindei commented on ISPN-1942:
------------------------------------
1. Agree, we should make the user remove the deprecated stuff when moving to the `stateTransfer` configuration.
2. `hash.rehashRpcTimeout` should have been equivalent to `stateTransfer.timeout` and `stateRetrieval.timeout`. However, I missed something in the LegacyConfigurationAdapter (namely the use of the `activated` flag) and this meant the `stateTransfer` settings are ignored when the configuration is adapted to the old style.
Ideally you should only need to use `stateTransfer` and `global.transport.distributedSyncTimeout` (which I forgot to give a more relevant name in 5.1). The old settings are only needed now because of the configuration translation bug.
> State transfer timeout confusion
> --------------------------------
>
> Key: ISPN-1942
> URL: https://issues.jboss.org/browse/ISPN-1942
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 5.1.3.CR1
> Reporter: Galder ZamarreƱo
> Assignee: Dan Berindei
> Fix For: 5.1.3.FINAL
>
>
> Several things are not right in the forum post above:
> 1. The XML file should not allow both stateRetrieval (deprecated) and stateTransfer to be defined:
> {code}<?xml version="1.0" encoding="UTF-8"?>
> <infinispan
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="urn:infinispan:config:5.1 http://www.infinispan.org/schemas/infinispan-config-5.1.xsd"
> xmlns="urn:infinispan:config:5.1">
>
> <global>
> <transport clusterName="hotrod-test" distributedSyncTimeout="16000000">
> <properties>
> <property name="configurationFile" value="/opt/infinispan-5.1.1.FINAL/etc/gossip-router-config.xml"/>
> </properties>
> </transport>
> <globalJmxStatistics enabled="true"/>
> </global>
>
> <default>
> <jmxStatistics enabled="true"/>
> <locking
> lockAcquisitionTimeout="16000000"
> />
>
> <clustering mode="replicated">
> <sync replTimeout="16000000"/>
>
> <!-- for replication -->
> <stateRetrieval timeout="16000000"/>
> <stateTransfer timeout="16000000"/>
> </clustering>
> </default>
>
> <namedCache name="A"/>
> <namedCache name="B"/>
> <namedCache name="C"/>
> <namedCache name="D"/>
> </infinispan>{code}
> 2. In spite of setting the stateTransfer timeout, state transfer is looking for hash.rehashRpcTimeout which by default is 10 minutes? @Dan, shouldn't the state transfer timeout be passed onto the hash.rehashTimeout?
> Also @Dan, do we have any docu on how this really should be configured in 5.1?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list