Am 15.12.2013 02:23, schrieb David Anderson: > > > On 09-Dec-2013 10:11 PM, Christian Beer wrote: > >> Almost everything needed for this is already in place. Changing the >> trickle_deadline handler to update another field or table is trivial. I >> can also add the logic of aborting or reactivating the task. The >> question is: do we add another field to the result table (last_contact) >> or create a new table for this. > > In principle no: > the host table has an rpc_time field (time of last RPC) and result links > to host. > Is this sufficient? > > -- David
This will only tell us the last contact of the host not the status of the task. Wouldn't it complicate the server scheduler that for each RPC it has to check all tasks for this host (in DB) with the list send in the RPC? This way it can cancel tasks that are not in the RPC-list and extend those that are near deadline. But we still don't know if the user paused the task and we extend the deadline although there is no computation done. Another problem I see is when the host is abandoned and never sends an RPC. Then the task is canceled by deadline, which may be far in the future. We would like to have a new task issued before this. This is kind of a variable deadline (server only) that needs to be checked by the transitioner. Maybe this is a better approach but would also mean to add a new field to the result table. A second server-only deadline that is extended by the scheduler with each RPC (if the task is in the RPC-list) and checked by the transitioner. This would only leave the paused task case which maybe is unsolveable from the server perspective. This would also mean that we don't need trickle up messages if the host is sending RPCs in a regular fashion. This variable deadline could be identical with the report deadline for projects not needing this feature and thus is not interfering with current behavior. Regards Christian _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
