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

Distributed execution timeout should not be linked to replication timeout

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 5.2.0.Beta1
    • 5.0.0.CR8
    • Clustered Executor
    • None

    Description

      Currently the timeout of a distributed execution is linked to the settings for the replication timeout (we have set the timeout to <sync replTimeout="120000"/> as a workaround). For long running tasks this is really annoying because you get an error back from the framework but the distributed tasks runs till the end without a problem.

      There should be an extra timeout for the execution of distributed tasks.

      Attachments

        Issue Links

          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-2287 Introduce DistributedTask abstraction enhancement for distributed executors

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              vblagoje Vladimir Blagojevic (Inactive)
              derry_jira Thomas Peuss (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: