Populating cache with pre-rendered page rollbacks content to initial data when a new container is up.

[LuizPelegrini]

Brief Description of the Bug
After revalidating a page (using ISR), if a new pod joins the cluster, it overwrites the page content back to its initial value when it was generated.

Severity
Major

Frequency of Occurrence
Always

Steps to Reproduce
Provide detailed steps to reproduce the behavior, including any specific conditions or configurations where the bug occurs:

1. Enable populating cache with pre-rendered page
2. Start a container A
3. Container A populates cache
4. Revalidate page X in container A (using on-demand revalidation)
5. Start container B
6. Container B populates cache (overwriting update in page X from step 4)

Expected
Revalidated page data should not get overwritten back when a new pod starts

Actual Behavior
Page data is overwritten whenever container starts

Environment:

• OS: MacOS
• Node.js version: 20.9.0
• @neshca/cache-handler version: 1.9.0
• next version: 14.2.8

Dependencies and Versions

• Redis: 4.7.1