Large Views Page Generates 502 Error on Acquia Cloud Next Platform

Created on 25 August 2022, over 2 years ago
Updated 19 October 2023, about 1 year ago

Problem/Motivation

We have a Views page with 1543 results that works fine on our Acquia Cloud Classic production server. When our development servers were migrated to Cloud Next, the one page failed. When the acquia_purge module is uninstalled, the page works fine. When the results are limited to 1100, the page works fine. Changing the Views caching to time-based or disabled doesn't help.

This is a blocker for us to migrate our production server to Cloud Next.

And no, the client won't allow the number of results to be limited.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Active

Version

1.2

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States papagrande US West Coast

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States keithdoyle9 Pennsylvania, USA

    Has this ever been resolved? We're running into the same error.

  • πŸ‡ΊπŸ‡ΈUnited States papagrande US West Coast

    @keithdoyle9, this ended up being a problem with too many cache tags on that client's page. Oddly, Cloud Next was worse than Cloud Classic when using the acquia_purge module.

    I solved it by removing the individual cache tags with the getCacheTagsToInvalidate() method on the custom entity. The entities are populated and displayed as a complete group so individual entity tags aren't needed.

    However, the problem remains in the module in that it shouldn't have a fatal error.

Production build 0.71.5 2024