[infinispan-issues] [JBoss JIRA] (ISPN-10124) transport lock-timeout description is slightly wrong in XSD schema
Dan Berindei (Jira)
issues at jboss.org
Wed Jun 26 09:49:00 EDT 2019
[ https://issues.jboss.org/browse/ISPN-10124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Berindei updated ISPN-10124:
--------------------------------
Sprint: DataGrid Sprint #30
> transport lock-timeout description is slightly wrong in XSD schema
> ------------------------------------------------------------------
>
> Key: ISPN-10124
> URL: https://issues.jboss.org/browse/ISPN-10124
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration, Core
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Reporter: Wolf-Dieter Fink
> Assignee: Dan Berindei
> Priority: Minor
>
> Form the infinispan-core xsd the transport lock-timeout description is like followed.
> <xs:complexType name="transport">
> <xs:attribute name="lock-timeout" type="xs:long" default="240000">
> <xs:annotation>
> <xs:documentation>
> Infinispan uses a distributed lock to maintain a coherent transaction log during state transfer or rehashing, which means that only one cache can be doing state transfer or rehashing at the same time.
> This constraint is in place because more than one cache could be involved in a transaction.
> This timeout controls the time to wait to acquire a distributed lock.
> </xs:documentation>
> </xs:annotation>
> </xs:attribute>
> This does not reflect the latest changes and should be updated
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the infinispan-issues
mailing list