[GH-ISSUE #80] Scaled instances and the deletion problem #344

New issue

Open

opened 2026-02-27 12:43:14 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 12:43:14 +03:00

Owner

Originally created by @geek-at on GitHub (Dec 29, 2018).
Original GitHub issue: https://github.com/HaschekSolutions/pictshare/issues/80

Now the codebase has been rewritten we can start and think about the problem with scaling pictshare: deleting content.

Imagine two Pictshare servers connected through a shared folder (ALT_FOLDER)

An image is requested frequently so both servers have a local copy and there is a copy in the shared folder.

If the user wants to delete the image, it's deleted off the server the user sent the request to and from the shared folder.

the second server never got any info about any deleted hash so they kept theirs.

Possible solutions:

Keep a list of deleted hashes in all storage controllers
Use some kind of centralized database that manages all hashes and stati
Make all nodes somehow communicate with each other

Originally created by @geek-at on GitHub (Dec 29, 2018). Original GitHub issue: https://github.com/HaschekSolutions/pictshare/issues/80 Now the codebase has been rewritten we can start and think about the problem with scaling pictshare: deleting content. Imagine two Pictshare servers connected through a shared folder (ALT_FOLDER) An image is requested frequently so both servers have a local copy and there is a copy in the shared folder. If the user wants to delete the image, it's deleted off the server the user sent the request to and from the shared folder. the second server never got any info about any deleted hash so they kept theirs. Possible solutions: - Keep a list of deleted hashes in all storage controllers - Use some kind of centralized database that manages all hashes and stati - Make all nodes somehow communicate with each other