starred/jellyfin

Fork 0

mirror of https://github.com/jellyfin/jellyfin.git synced 2026-01-23 23:20:51 +01:00

Metadata Refreshing is not able to be rate limited #6161

New issue

Open

opened 2025-12-22 03:44:42 +01:00 by backuprepo · 3 comments

backuprepo commented

2025-12-22 03:44:42 +01:00

Owner

Originally created by @PhantomPhoton on GitHub (Aug 1, 2024).

This issue respects the following points:

This is a bug, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found here.
This issue is not already reported on GitHub (I've searched it).
I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
I agree to follow Jellyfin's Code of Conduct.
This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Description of the bug

I recently changed metadata providers and ran a scan to update missing metadata, however, our internet connection is very limited and the scan is triggering hundreds of simultaneous requests, flooding the network connection and making it unusable. This most certainly isn't nice behavior for our metadata providers. There should be a sane default for the maximum number of outbound requests to a provider and hopefully be able to be adjusted for those of us on very slow connections.

Reproduction steps

Scan for missing metadata on a library with a lot of missing metadata. Watch the active number of connections increase to very high levels.

What is the current bug behavior?

I've seen over 256 active simultaneous requests at a time. This is causing failures as sockets time out due to being flooded by too much traffic.

What is the expected correct behavior?

Less simultaneous requests and so we can make slow, steady progress

Jellyfin Server version

10.9.8+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

10.9.8

Specify the build version

10.9.8

Environment

- OS: Ubuntu 24.04
- Linux Kernel: 6.8
- Virtualization: None
- Clients: Browser
- Browser: Firebox
- FFmpeg Version: 6.0.1-Jellyfin
- Playback Method: Depends
- Hardware Acceleration: None
- GPU Model: None
- Plugins: None
- Reverse Proxy: None
- Base URL: None
- Networking: Host
- Storage: Local

Jellyfin logs

Example output when things timeout

[WRN] [174] Emby.Server.Implementations.Library.LibraryManager: Cannot fetch image from https://image.tmdb.org/t/p/original/HASH_HERE.jpg. Http status code: null

FFmpeg logs

No response

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

Thank you all very much for the wonderful software. I really appreciate your time and consideration for my report.

Originally created by @PhantomPhoton on GitHub (Aug 1, 2024). ### This issue respects the following points: - [X] This is a **bug**, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found [here](https://jellyfin.org/contact/). - [X] This issue is **not** already reported on [GitHub](https://github.com/jellyfin/jellyfin/issues?q=is%3Aopen+is%3Aissue) _(I've searched it)_. - [X] I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue. - [X] I agree to follow Jellyfin's [Code of Conduct](https://jellyfin.org/docs/general/community-standards.html#code-of-conduct). - [X] This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one. ### Description of the bug I recently changed metadata providers and ran a scan to update missing metadata, however, our internet connection is very limited and the scan is triggering hundreds of simultaneous requests, flooding the network connection and making it unusable. This most certainly isn't nice behavior for our metadata providers. There should be a sane default for the maximum number of outbound requests to a provider and hopefully be able to be adjusted for those of us on very slow connections. ### Reproduction steps Scan for missing metadata on a library with a lot of missing metadata. Watch the active number of connections increase to very high levels. ### What is the current _bug_ behavior? I've seen over 256 active simultaneous requests at a time. This is causing failures as sockets time out due to being flooded by too much traffic. ### What is the expected _correct_ behavior? Less simultaneous requests and so we can make slow, steady progress ### Jellyfin Server version 10.9.8+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number 10.9.8 ### Specify the build version 10.9.8 ### Environment ```markdown - OS: Ubuntu 24.04 - Linux Kernel: 6.8 - Virtualization: None - Clients: Browser - Browser: Firebox - FFmpeg Version: 6.0.1-Jellyfin - Playback Method: Depends - Hardware Acceleration: None - GPU Model: None - Plugins: None - Reverse Proxy: None - Base URL: None - Networking: Host - Storage: Local ``` ### Jellyfin logs ```shell Example output when things timeout [WRN] [174] Emby.Server.Implementations.Library.LibraryManager: Cannot fetch image from https://image.tmdb.org/t/p/original/HASH_HERE.jpg. Http status code: null ``` ### FFmpeg logs _No response_ ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information Thank you all very much for the wonderful software. I really appreciate your time and consideration for my report.

backuprepo added the

enhancement

label 2025-12-22 03:44:42 +01:00

backuprepo commented

2025-12-22 03:44:45 +01:00

Author

Owner

@felix920506 commented on GitHub (Aug 1, 2024):

What CPU are you using?

Also, we recommend that you head to our forum or chat rooms for some way to mitigate the issue, such as configuring QoS or some per client bandwidth limit for the entire network. https://jellyfin.org/contact

@felix920506 commented on GitHub (Aug 1, 2024): What CPU are you using? Also, we recommend that you head to our forum or chat rooms for some way to mitigate the issue, such as configuring QoS or some per client bandwidth limit for the entire network. https://jellyfin.org/contact

backuprepo commented

2025-12-22 03:44:48 +01:00

Author

Owner

@gnattu commented on GitHub (Aug 1, 2024):

I think you can limit concurrency for the whole library scan in Dashboard->General->Scroll down to Performance.

Set it to a lower value will also limit the API request frequency when you have a CPU with a lot of cores.

@gnattu commented on GitHub (Aug 1, 2024): I think you can limit concurrency for the whole library scan in Dashboard->General->Scroll down to Performance. Set it to a lower value will also limit the API request frequency when you have a CPU with a lot of cores.

backuprepo commented

2025-12-22 03:44:51 +01:00

Author

Owner

@PhantomPhoton commented on GitHub (Aug 1, 2024):

Ahh! Thank you for that hint, I am running on a multicore system with 44/88 physical/logical, and will try to reduce the value.

My main point was less that it wasn't changeable on my end, but more that it's not very nice to flood our metadata providers, however, I see that it's more of an issue with my system rather then a systemic issue. Please accept my apology for not knowing about those specific settings.

@PhantomPhoton commented on GitHub (Aug 1, 2024): Ahh! Thank you for that hint, I am running on a multicore system with 44/88 physical/logical, and will try to reduce the value. My main point was less that it wasn't changeable on my end, but more that it's not very nice to flood our metadata providers, however, I see that it's more of an issue with my system rather then a systemic issue. Please accept my apology for not knowing about those specific settings.

backuprepo referenced this issue

2025-12-22 08:14:46 +01:00

[PR #6161] [MERGED] Bump SQLitePCL.pretty.netstandard from 3.0.1 to 3.1.0 #10660

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#6161

No description provided.

Rows
Columns