Please allow Interval adjustment for Task: Refresh Artists.

hikaricore asked for this feature about 2 years ago — 29 comments

hikaricore commented about 2 years ago

Table Name - ScheduledTasks
ID #5 - NzbDrone.Core.Music.Commands.RefreshArtistCommand
Interval - 1440

Ideally, especially for those of us for larger libraries or limited resources, this would be adjustable by the number of days we see fit. I've attempted to edit this manually within lidarr.db, but Lidarr does not seem to respect this change and either overwrites or ignores it. For some users, even disabling it may be appreciated as noted here:

Edit: Just as a point of reference, this is what we're up against:

| cameronrbrown commented about 2 years ago

I concur. It's often the only thing happening on my hard drives. Let them rest

| streat90 commented about 2 years ago

I agree, with large libraries this results in an effectively endlessly running task.

| tro-co commented almost 2 years ago


| dcman commented almost 2 years ago

I agree.

| quindarious-gooch commented almost 2 years ago

Thumbs up. I often find this process smashing my server at the expense of other more time critical apps like Plex.

| hikaricore commented almost 2 years ago

Even an option to cancel it from the Tasks page would help in the meantime. I'm trying to update Lidarr, but the update won't process until the Refresh Artists task completes 12+ hours (we're 15 minutes into the full refresh of my 558 artists) from now.

| Keldwan commented almost 2 years ago

I have 1500+ artists, Refresh Artists literally runs 24/7 on my system. I finally ended up setting the service to manual start so it will only run when I want it to. I actually don't even monitor a lot of the artists I have as they are not producing new content anymore. My suggestion would be to only do a refresh of artists that are in monitor status as that content is the most likely to change.

| hikaricore commented almost 2 years ago

Sorry, I meant to say 120+ hours. XD

| al-bondigas commented almost 2 years ago

+1, this missing functionality is the only thing keeping me from using Lidarr.

scootied commented almost 2 years ago

+1 I've got 1500+ artists and my scan never ends!

scootied commented almost 2 years ago

I've gone back to headphones until this is sorted out. It really makes the app unusable which is a shame as it's awesome apart from this issue which, I am guessing, is a 5 minute fix for anyone who knows the source code (which I unfortunately don't). I'd pay $10 to get this fixed ASAP :)

| romprod commented almost 2 years ago

Yeah ditto on this. I can't understand why there's a need to keep re-scanning it anyway. Surely it's scanned once and that's it unless changes have been detected? 100% stopping me from using this over Headphones.

| streat90 commented almost 2 years ago

Agreed, this is the only thing holding me back from using Lidarr

| Faeton73 commented almost 2 years ago

Yes, this feature is a must! Over 1800+ artists in my library, and lidarr hogs one of the cpus continuously

glberen commented over 1 year ago

Yes, please!

stoofz commented over 1 year ago

Yes Please!!

| kzuidema commented over 1 year ago

Yes Please!

| jeffreyswiggins commented over 1 year ago

Please make this happen or I will have to stop using LIDARR or kill it all week and run the application 1 day a week. I have so many tracks and artists it never finishes and it is pounding my NAS all day and night

| hikaricore commented over 1 year ago

That's pretty much what I've resorted to. Starting up Lidarr weekly or monthly, then shutting it down. It's just not feasible to let it scan for 5-7 days straight all the time.

Concreteseller commented over 1 year ago

If someone did pick up on this, perhaps the scan could also pickup where it left off between reboots also. with a refresh taking a day only to start over when the system hiccups. A button to pause, start/stop or mark the scan complete would be nice. please excuse if this has been mentioned before

| ConfusedTA commented over 1 year ago

Adding my +1 here for this as a configurable option, my box has been running non-stop just refreshing artists.

| gcoan commented over 1 year ago

Same here +1

| hikaricore commented over 1 year ago

It looks like this commit has adjusted the way that scanning for Refresh Artists works:

I don't wanna jump the gun here, but after seeing an automatic and manual scan complete in a very short time on my setup, I'm optimistic that this may resolve much of the trouble we've been having here. Can anyone else confirm?

| hikaricore commented over 1 year ago

To confirm, with the update I had mentioned previously I'm seeing a scan only taking around 4-5hrs. While it would still be nice to change the value from 24hrs to something else, Lidarr is now much calmer and precise with its scans.

| astro7467 commented 10 months ago

Like others my library is running 24/7 for this currently and making the rest of the app near useless. Seems to take 3 days to run on my library. Either needs smart logic to batch update portions for a period of time or manual scheduling of preferred timing.

| BinsonBuzz commented 9 months ago

I've just created a fresh installation to give Lidarr another go, and I've just realised this is probably why it rarely imports tracks as it's stuck refreshing the initial artists I added - I've got about 500 'Refresh Artist' tasks 'Queued' 11 hours ago, so I'm guessing it'll take about another day to finish.

Once it's done the initial refresh i.e. downloaded all the album data, will subsequent refreshes be faster?

| bigdork commented 5 months ago

+1, man this really makes lidarr almost worthless with large libraries on network storage - PLEASE FIX!

mprachar commented about 1 month ago

+1 as well

Join the discussion!

with GitHub to comment