couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Cottlehuber (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1441) _rewrite handler loops cause cpu load and swap of death
Date Thu, 15 Mar 2012 20:52:37 GMT


Dave Cottlehuber commented on COUCHDB-1441:

Thanks Ronny for raising this!

I don't see how we could deterministically detect this prior to storing the updated ddoc (halting
The question then is can the rewriter track number of traverses and eventually die?
Or do we mark as DNF and note in the appropriate place that you can easily shoot yourself
in the foot here?
> _rewrite handler loops cause cpu load and swap of death
> -------------------------------------------------------
>                 Key: COUCHDB-1441
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>         Environment: debian testing
>            Reporter: Ronny Pfannschmidt
> when creating a simple _rewrite loop, the db will start to eat cpu and take more &
more memory
> for testing i created:
> {"_id":"_design/loopa","rewrites":[{"from":"","to":"../loopb/_rewrite"}]}
> {"_id":"_design/loopb","rewrites":[{"from":"","to":"../loopa/_rewrite"}]}
> accessing $dburi/_design/loopa/_rewrite/ will start the loop

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message