[
https://issues.apache.org/jira/browse/COUCHDB-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725324#action_12725324
]
Paul Joseph Davis commented on COUCHDB-397:
-------------------------------------------
Now I'm confused even more.
I get the notion of how terminate_child is working in terms of the
terminate/restart semantics but you're losing me with the discussion about
linking the processes to get them to shutdown when couch_server goes down. Why
would we consider that when we can instead restart the secondary services
directly as trunk does currently and the patch you have on 398 does. Also, does
the patch for 398 mean that that works? In your earlier comment you made it
sound like that didn't work.
Regardless, I definitely think you're right that we should sit down and discuss
what exactly needs to get restarted on on a call to _restart. On the other
hand, should _restart even be enabled by default? AFAIK it was just put in for
testing, are there use cases for making it available?
> POST _restart only restarts couch_server process
> ------------------------------------------------
>
> Key: COUCHDB-397
> URL: https://issues.apache.org/jira/browse/COUCHDB-397
> Project: CouchDB
> Issue Type: Bug
> Affects Versions: 0.9
> Reporter: Adam Kocoloski
> Assignee: Adam Kocoloski
>
> Perhaps this is by design, but POSTing to /_restart only restarts the
> couch_server process. It does not restart any of the other myriad processes
> CouchDB relies on for operation. In particular, this causes the stats test
> suite to occasionally fail, because the stats counters do not get reset. The
> test that fails is
> Assertion 'open_databases > 0 && max >= open_databases, name' failed: should
> keep the same number of open databases when reaching the max_dbs_open limit
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
