Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Roland Egedi 8 posts 108 karma points
    Apr 30, 2020 @ 12:10
    Roland Egedi
    0

    Published Cache Status not OK

    We went Live with our first Umbraco 8 (with 2 languages) this week. But the message under "Published Cache Status" makes me a bit nervous... Every day it changes to "Database cache is NOT ok (rebuild?)." I rebuild it every day manually so far.

    • Is this a problem? Or is this expected behavior?
    • What can I do to check why this is happening? Are there any lists or something I can check against? Or tutorials?
    • What do the numbers actually mean? How to tell if that is good or bad?

    ("ContentStore contains 619 items and has 4 generations and 1 snapshot. MediaStore contains 578 items and has 7 generations and 1 snapshot.")

    Is it possible to trigger Database Cache-rebuild / Memory Cache-rebuild myself? Eg by having a job that does this every night? (I guess that shouldn't be the recommended way but as a temporary workaround)

    I have seen the message during development also, but thought it had to do with all strange codes/changes in Dev-env.

    The only "strange" thing I can think of we are doing is that we have a scheduled job that import/create new nodes/pages every day.

    (Using ContentService with CreateContent and the SaveAndPublish or GetById if it's an update)

    We also have members that register. (we have ca 45,000 members, a couple of new ones every day are created)

    And then of-course editors who create/update pages.

    Any help or suggestions would be greatly appreciated!

    Umbraco 8.5.3.

  • David Zweben 231 posts 688 karma points
    Jul 15, 2020 @ 14:43
    David Zweben
    0

    Having the same issue here. Can anyone point us in the right direction to troubleshoot this?

    My setup is similar in that it has Hangfire scheduled tasks, and members signing up (very few, though). It seems to mostly happen on Live after a deploy from Dev. It doesn't always seem to result in visible issues, but sometimes nodes go missing and the cache has to be reloaded or rebuilt.

  • This forum is in read-only mode while we transition to the new forum.

    You can continue this topic on the new forum by tapping the "Continue discussion" link below.

Please Sign in or register to post replies