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

Invocations waiting for a new topology should resume in parallel

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Out of Date
    • 8.2.11.Final, 10.0.0.Alpha2, 9.4.5.Final
    • 10.0.0.Beta4
    • Core
    • None

    Description

      When a command requires a topology newer than the current topology, it uses StateTransferLock.transactionDataFuture() to wait for the newer topology. When the tx data is received for the newer topology, some (most?) of the waiting operations do not use a separate executor, instead they are all resumed on the thread that received the tx data. If some operations block (e.g. because of a store), it could take a very long time to finish all the blocked operations.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: