]
Vladimir Blagojevic updated ISPN-1153:
--------------------------------------
Git Pull Request:
Validate relationship between transport related timeouts
--------------------------------------------------------
Key: ISPN-1153
URL:
https://issues.jboss.org/browse/ISPN-1153
Project: Infinispan
Issue Type: Task
Components: Configuration
Affects Versions: 5.0.0.BETA1
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 5.0.0.CR5
We have to form equality relationships between all our transport related timeouts and
verify that
the make sense as configuration instance is being processed.
Alphabetically we have the following timeouts in our configuration elements:
<async>: flushLockTimeout, shutdownTimeout
<deadlockDetection>: spinDuration
<hash>: rehashRpcTimeout
<locking>:lockAcquisitionTimeout
<singletonStore>:pushStateTimeout
<stateRetrieval>:logFlushTimeout, timeout, initialRetryWaitTime
<sync>:replTimeout
<transaction>:cacheStopTimeout
<transport>: distributedSyncTimout
My suggestions so far:
flushLockTimeout < shutDownTimeout (async) < cacheStopTimeout
spinDuration < lockAcquisitionTimeout < replTimeout < rehashRpcTimeout
replTimeout < distributedSyncTimout < <stateRetrieval>:timeout
--
This message is automatically generated by JIRA.
For more information on JIRA, see: