-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AniDB Creators - Ban and performance #1175
Comments
Update: Ban occured each day after completing ~3,000 tasks. |
It shouldn't have been scheduled at startup in the first place. Edit: if you don't actually need the creator (not VA, it's for other staff) images immediately, you can clear the queue. If you update the anidb info of a series, the images will be downloaded them. |
Thanks for the info, at this point I am commited to it completing.
Okay, than should I go ahead and close the issue? |
Yeah we can close this issue for now, if you notice any other weird activity, we can look into it further. |
@Rand-Random just letting you know that the new optional action to schedule the get creator jobs now have a progress indicator in the log. the new action also won't schedule the any creators which have had the job previously ran, in case anyone want (or need) to run the action at some point, then they can rest assured that it won't schedule every creator once again, as it will only schedule the ones with missing metadata. |
Version of Shoko Server: 4.2.2.147 (f469fb2)
The new addition of AniDB creators enhancement took 33 minutes for the database update.
Since it was taking so long, maybe consider some kind of progress indicator.
It stood on the same message for over half an hour which may make people nervous and believe shokoserver is stuck.
After the success of the datbase update, 12,634 creators were in the queue to process.
A good night sleep later, and I have a anidb udp ban.
5 hours 30 minutes later and still 9,631 Tasks to go.
The text was updated successfully, but these errors were encountered: