How to abort tasks

solling2
solling2
Joined: 20 Nov 14
Posts: 108
Credit: 255,763,556
RAC: 596,082
Topic 215224

Is there a way to abort tasks in the web account? I know there's a chance to do that in the Boinc manager. However,  I'm trying to build a fallback cruncher. In between I had a working system. It downloaded tasks for 1.5 days, (which seems a lot to me for beginners, wouldn't 0.1 be better?) - Boinc default setting. That system however showed a severe instability unrelated to Einstein, so I aborted the whole system. Still though, in the account I see that those many tasks are still in the waiting for result status, obviously for 14 days until no result by deadline. If there was a way to abort those tasks, they could be sent to another machine right now.

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 4,748
Credit: 26,026,230,798
RAC: 35,158,336

solling2 wrote:Is there a way

solling2 wrote:
Is there a way to abort tasks in the web account?

Not that I know of.  The design is for anything like that to happen at the client end and then be 'reported'.

Quote:
It downloaded tasks for 1.5 days, (which seems a lot to me for beginners, wouldn't 0.1 be better?) - Boinc default setting.

I have no idea what the default is these days.  I install a complete template which has all settings customised the way I want (cache is 0.2+0.01 for starters, also NNT is set) so I know I can't get any nasty surprises when first launched.  I always thought the default used to be about 0.5 days or less.  I'm quite surprised that it's 1.5.  That could be a very large number of tasks if the initial estimate is very low.

Quote:
That system however showed a severe instability unrelated to Einstein, so I aborted the whole system.

Did you actually abort and report or did you just stop BOINC and delete stuff locally?

Quote:
Still though, in the account I see that those many tasks are still in the waiting for result status, obviously for 14 days until no result by deadline. If there was a way to abort those tasks, they could be sent to another machine right now.

You could probably achieve just that if you still have the BOINC directory on that host.  If you fire it up and allow it to contact the server, those tasks that are still there on the website should be sent back to you as 'lost tasks' in batches of 12 each time your client contacts the server.  Force it to contact with 'update'.  When you have them all, highlight the lot and click the abort button.  Then click 'update' to report them all.  When that is complete, they will all be shown as aborted on the website and will be immediately available for redistribution.

 

Cheers,
Gary.

mikey
mikey
Joined: 22 Jan 05
Posts: 4,712
Credit: 489,128,693
RAC: 566,613

solling2 wrote:Is there a way

sorry wrong thread

 

solling2
solling2
Joined: 20 Nov 14
Posts: 108
Credit: 255,763,556
RAC: 596,082

In that case I had to abort

In that case I had to abort the whole OS. Thx for confirming that there's no access to task status via web account. I intend to do better next time. :-)

mmonnin
mmonnin
Joined: 29 May 16
Posts: 251
Credit: 573,553,512
RAC: 1,647,524

I think BOINC install default

I think BOINC install default is still 1 + 3 days for a queue.

solling2
solling2
Joined: 20 Nov 14
Posts: 108
Credit: 255,763,556
RAC: 596,082

mmonnin schrieb:I think BOINC

mmonnin wrote:
I think BOINC install default is still 1 + 3 days for a queue.

I was wondering what factors determine the number of tasks that are sent to a client. Seems there is a coaction of settings in the web account and settings in the Boinc manager menu. Maybe the policy is to provide enough work for a client for a day. As soon as time limits become another determining factor, it seems the project server will dim the send-outs. Hence abortions should be exceptions.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.