Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 1
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 3471 times and has 0 replies Next Thread
knreed
Former World Community Grid Tech
Joined: Nov 8, 2004
Post Count: 4504
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
No work being sent [Resolved]

We experienced an issue last night where the "feeder" running on our server infrastructure stopped running. This has prevented work from being distributed over the past several hours. We have started it up again and work is being sent out again. Due to the length of time that it was stopped, there are many clients requesting work and it make take a couple of attempts for your client to get work.

The "feeder" locates tasks that are ready to send in the database and puts them into a shared memory cache that is accessed by the scheduler when your client makes a request for work. This architecture allows the system to handle higher volumes than if the scheduler accessed the database to find new work on every client request. The feeder has typically been a very stable process and we will investigate what happened. Thank you for your patience.
----------------------------------------
[Edit 1 times, last edit by knreed at Dec 11, 2013 3:25:23 PM]
[Dec 10, 2013 1:43:10 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread