couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Dionne <>
Subject Re: Long running task status monitoring
Date Fri, 23 Jan 2009 10:20:10 GMT
This is very cool, I'll check it out.

After a build with yesterday's changes I started seeing these  
exceptions again:

This was fixed (#213) a few days ago. I lowered max_open_databases on  
my machine to 50 and it still occurs. It only occurs once when  
running the tests from Futon, which all pass. However when running  
the tests standalone from the runner script, you'll see two or three.  
Running these requires the patch I submitted to couch_js.c

I'll try to run this down (no pun intended :)


On Jan 22, 2009, at 11:18 PM, Damien Katz wrote:

> I just checked in code to allow the checking of the status of long  
> running tasks, like view indexes and compaction.
> During a long view build or compaction, if you want to see the  
> status of what's happening, simply GET _active_tasks and you'll get  
> back a list of JSON objects describing the currently running tasks.
> Example results while 2 tasks are running:
> [{"type":"Database Compaction","task":"speed","status":"Copied  
> 10001 of 39001 changes (25%)","pid":"<0.78.0>"},
> {"type":"View Group Indexer","task":"speed _design/ 
> test","status":"Processed 0 of 39001 changes (0%)","pid":"<0.91.0>"}]
> We should probably add task tracking code for replication as well.
> -Damien

View raw message