Uploaded image for project: 'Forrest'
  1. Forrest
  2. FOR-732

Changing the locationmap after a resource not found error has no effect

        Details

        • Type: Bug
        • Status: Resolved
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 0.8
        • Fix Version/s: 0.8
        • Component/s: Locationmap
        • Labels:
          None

          Description

          If a resource is requested and is not found, then a change is made to the locationmap to ensure the resource is found, Forrest requires a reboot for the change to be noted.

          This may be as a result of in-progress work on FOR-711 or may be unrelated.

            Issue Links

            depends upon

            Sub-task - The sub-task of the issue FOR-711 Cache results from the Locationmap

            • Critical - Crashes, loss of data, severe memory leak.
            • Resolved

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              williamstw Tim Williams added a comment -
              I'm pretty sure it is a result of caching. We're caching the null results too right now, this is important because of having an exists selector. I think null's shouldn't be cached at the locationmap module level and should probably be done at a lower level so that it can be done more granularly.
              --tim
              Show
              williamstw Tim Williams added a comment - I'm pretty sure it is a result of caching. We're caching the null results too right now, this is important because of having an exists selector. I think null's shouldn't be cached at the locationmap module level and should probably be done at a lower level so that it can be done more granularly. --tim
              Hide
              Permalink
              williamstw Tim Williams added a comment -
              When it's detected that the locationmap is not valid, the cache needs to be flushed or the reload of the locationmap will have no effect. This is easy enough for the core locationmap but as a result of having caching at the module level, there's no way to flush the cache based on a mounted locationmap becoming invalid.

              *These are more or less notes so that I have something to make me remember where I was at with this.
              --tim
              Show
              williamstw Tim Williams added a comment - When it's detected that the locationmap is not valid, the cache needs to be flushed or the reload of the locationmap will have no effect. This is easy enough for the core locationmap but as a result of having caching at the module level, there's no way to flush the cache based on a mounted locationmap becoming invalid. *These are more or less notes so that I have something to make me remember where I was at with this. --tim
              Hide
              Permalink
              williamstw Tim Williams added a comment -
              I believe the simple TTL fix r474646 will suffice for now. Unfortunately, the commit message is linked to the parent issue and not this one.
              Show
              williamstw Tim Williams added a comment - I believe the simple TTL fix r474646 will suffice for now. Unfortunately, the commit message is linked to the parent issue and not this one.

                People

                • Assignee:
                  williamstw Tim Williams
                  Reporter:
                  rgardler Ross Gardler
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Development