There's no kill button. The job would have to be killed by an operator (a phabricator request is probably in order). As a general option, it would be a bad idea to have a general kill process, what would be more useful would be a process for an end user to kill/pause a job request using a given job ID. There are no current plans to implement anything like this, something to add to a Stage 2 if that ever happens.
Out of interest, how many processing threads were chosen in GWT for the job? It may be an idea if the input page is changed to default to 2 threads and there are warnings if you have more than 8 or so. I can imagine 20 processing threads causing a server issue for large files and in practice I used 4 or 5 for my largest upload jobs; probably something to usefully add to the user guide.
Fae
On 1 June 2015 at 10:35, Charles Andrès charles.andres@wikimedia.ch wrote:
Ok, guys are looking into it right now, but it doesn’t seems to be so easy to do.
Stupid question, is there already discussion to have an « emergency button » to stop a GWToolset job?
charles