Sign in Register
Copied to clipboard

Flag this post as spam?

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


  • Moray McConnachie 3 posts 73 karma points
    May 06, 2016 @ 08:28
    Moray McConnachie
    0

    Bug? - unpublishing nodes on front-end servers in advanced load balancing set-up

    This feels like a bug, but thought I'd ask here first.

    We're using the advanced load balancing technique described at https://our.umbraco.org/documentation/getting-started/setup/server-setup/load-balancing/flexible-advanced, ie a read-write back-office instance and twin redundant read-only front-end instances each on a separate back-end server, pointing at a mirrored redundant SQL server.

    It all works fine when publishing new nodes, editing nodes, deleting nodes etc.

    However when unpublishing nodes, it only works on the back office and never makes the change at the front-end.

    We can tell the front-end servers are not updating because app_data/umbraco.config on the front end servers never sees the relevant node removed while other changes are being replicated in the same time-frame.

    Feels like a bug...

    Copy Link
  • Dennis Adolfi 1082 posts 6449 karma points MVP 6x c-trib
    Jul 10, 2017 @ 14:15
    Dennis Adolfi
    0

    Hi Moray.

    Did you find an answer to this?

    Experiencing similar issue on a advanced load balancing enviroment.

    Copy Link
  • Wojciech 4 posts 74 karma points
    May 18, 2018 @ 13:17
    Wojciech
    0

    Same here - Let me know guys if you find the solution.

    At our env - Unpublish manually - works. Timed - does not :(

    Copy Link
  • Wojciech 4 posts 74 karma points
    Jun 06, 2018 @ 08:53
    Wojciech
    0

    Well - I would like to post resolution for this, what helped in our case

    Firstly - our infrastructure. Hosting on Azure, one master server on single app service, and 3 frontend nodes on separate app service. Files also stored in Azure.

    1. read deeply the manual about load balancing and flexible load balancing. Few steps weren't performed.
    2. override IServerRegistrar2 Interface (as pointed in manual) to designate master and slave servers
    3. we had Umbraco 7.7.6 and it seems that version 7.7 was buggy., solved in version 7.7.7 http://issues.umbraco.org/issue/U4-10715

    So all steps (verify the configuration and update the Umbraco to 7.7.7) did the trick ;)

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft