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

Parallel purger threads will not be locked globally in FileCacheStore

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 5.0.0.CR8
    • Eviction, Loaders and Stores
    • None
    • Hide

      None

      Show
      None

    Description

      The function FileCacheStore.purgeInternal() aquires a global lock and releases it after completion.

      When multiThreadedPurge is true (which cannot be the case due to another bug, that I'll post later), the lock will be released BEFORE purging has completed.
      This is caused by the implementation, that starts N purger threads in parallel but does not wait for them to complete (as I think).

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. ISPN-1287 Certain configuration options not properly unmarshalled in CacheLoaderConfig

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-1288 FileCacheStore should lock individual files when purging, rather than acquire a global lock

          • 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

          Task - Represents a small unit of work that is not end-user facing. ISPN-1290 Expiration thread wakeup interval default is too short

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • To Do

          Activity

            People

              manik_jira Manik Surtani (Inactive)
              snazy0 Robert Stupp (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: