[
https://issues.apache.org/jira/browse/COUCHDB-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230530#comment-13230530
]
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 pb).
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: https://issues.apache.org/jira/browse/COUCHDB-1441
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
