What might be causing excessive DNS queries for "metadata.provider.plex.tv"? | Seerr | Page 1

flat fox Apr 30, 2024, 6:34 PM

#

I've noticed that when using overseerr I see tons of DNS requests for "metadata.provider.plex.tv". Specifically the more often I run the Plex jobs in overseerr the more requests there are - which makes sense.

However, the scale is absurd. For my relatively small server (~1500 movies, ~300 shows), I'm seeing ~1.5 million requests in pihole per day for metadata.provider.plex.tv.

The only culprit I've found is overseerr (indirectly, perhaps) - when I configure "Plex Recently Added Scan" and "Plex Full Library Scan" to the lowest intervals (and run "Plex Watchlist Sync" every min by making an API call) I see ~800 rpm in pihole for the metadata domain. This seems too high for what shouldn't trigger metadata updates. For now I have set these to 15 mins and 2 hours respectively (and "Plex Watchlist Sync" to 5 minutes).

So what might be causing this?

sweet whale Apr 30, 2024, 7:22 PM

#

Strange, doesn't help your situation, but just had a quick look at my PiHole and I don't see a single request for anything plex related.

flat fox Apr 30, 2024, 8:08 PM

#

Is your Plex using pihole for sure?

sweet whale Apr 30, 2024, 8:23 PM

#

The windows VM running the rr stack and Plex are definitly set up to go through the PiHole.
No reason why it shouldn't.
Find it odd though there are no queries for the last 2 days when I know it was active today

flat fox Apr 30, 2024, 8:24 PM

#

It should definitely have some

flat fox Apr 30, 2024, 9:07 PM

#

Okay through trial and error I found that running Plex Watchlist Sync causes these DNS queries.

Can a dev explain why this is causing so many DNS queries to metadata.provider.plex.tv? Shouldn't stuff be cached within overseerr?

#

Methodology: Running Plex Watchlist Sync every 5 minutes results in ~1200 DNS requests, but running every 1 min resulted in 1100 requests within 2 minutes.

stray heart May 2, 2024, 5:54 PM

#

The Plex Recently Added scan just gets the most recently added items from Plex, so it's not an expensive operation at all.
A full library scan though, will go through every single item in all your libraries, so I'm confused as to why you set it to 2 hours. If you have your Plex server configured correctly, all additions to your libraries will be picked up by the Plex Recently Added scan, and the Full Library Scan will barely be needed.
As for the watchlist sync, whenever you are on the discover page/watchlist slider, it will update for your user very fast. The watchlist sync is just to sync all users' watchlists.

While you have a moderate sized content library, the frequency of the jobs is just too much. Why did you decide to trigger these jobs so frequently? Did you have issues with content not appearing fast enough?

#What might be causing excessive DNS queries for "metadata.provider.plex.tv"?