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

Introduce a separate thread pool for async cache operations

    XMLWordPrintable

Details

    Description

      At the moment, it is very easy for an application to start a huge number of putAsync operations and fill the transport executor's thread pool, delaying internal work such as state transfer. Increasing the size of the transport executor's thread pool won't work, because that would in turn fill the remote commands and JGroups' OOB thread pools, with the same effect.

      If the cache async operations used a different thread pool, it would be possible to configure more remoteCommandsThreadPool threads than asyncOperationsThreadPool threads, avoiding this problem.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: