Uploaded image for project: 'CernVM'
  1. CernVM
  2. CVM-1777

Incorrect implementation of locking in geo api

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • High
    • Resolution: Fixed
    • CernVM-FS 2.6
    • CernVM-FS 2.6.1
    • CVMFS
    • None
    • ANY

    Description

      I happened to notice that the lock implementation in the geo api is incorrect and completely ineffective; a new lock object is allocated every time, instead of sharing it between threads.  I am amazed that it passes the parallelism test in 614-geoservice.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. CVM-1739 New geodb is not loaded into the geo api until apache is reloaded

          • Medium - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Task - A task that needs to be done. CVM-1349 Geo api needs to cache DNS lookups, especially failures

          • High - Major loss of function.
          • Closed

          Activity

            People

              dwd Dave Dykstra
              dwd Dave Dykstra
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                Actual End: