Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <1910090626.1246381727395.JavaMail.jira@brutus>
Date: Tue, 30 Jun 2009 10:08:47 -0700 (PDT)
From: "Adam Kocoloski (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Commented: (COUCHDB-397) POST _restart only restarts
 couch_server process
In-Reply-To: <1962165703.1246290407512.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725704#action_12725704 ] 

Adam Kocoloski commented on COUCHDB-397:
----------------------------------------

Hi Paul, I tried terminating all secondary services, but it ended up getting a bit complicated.  couch_httpd is one of those services, so we end up shutting down the connection that accepted the request.  I tried to work around this by spawning a fun to trigger the restart.  This allowed me to respond to the request to _restart, but the test suite still ran into problems because modern browsers will make multiple connections to the CouchDB server in order to run the tests.

I think we can develop a graceful shutdown procedure that closes all connections appropriately and and restarts things, but in the interests of getting 0.9.1 out the door I just changed restart_core_server() to explicitly restart the stats processes.

> 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.