Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-12924

State transfer timeout should be validated

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 13.0.0.Dev01
    • 12.1.0.Final
    • Core
    • None

    Description

      The state transfer timeout attribute doesn't have any validation: even 0 is a valid value, even though caches with a 0 timeout will be unable to start.

      To make matters worse, Wildfly has unified the timeout and await-initial-transfer attributes: timeout="0" means await-initial-transfer is disabled and timeout is infinite. Wildfly has better visibility, so users may see the Wildfly configuration documentation first and assume it applies to vanilla Infinispan.

      To prevent accidents, StateTransferConfigurationBuilder should validate that the state transfer timeout is at least as large as remote-timeout.

      We should also consider using state transfer timeout only for the initial transfer wait, merged with await-initial-transfer like in Wildfly, and using remote-timeout in other places that use the state transfer timeout now.

      Attachments

        Activity

          People

            dberinde@redhat.com Dan Berindei (Inactive)
            dberinde@redhat.com Dan Berindei (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: