Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 34134 invoked from network); 2 May 2010 14:37:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 May 2010 14:37:22 -0000 Received: (qmail 93330 invoked by uid 500); 2 May 2010 14:37:22 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 93260 invoked by uid 500); 2 May 2010 14:37:21 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 93252 invoked by uid 99); 2 May 2010 14:37:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 May 2010 14:37:21 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 May 2010 14:37:18 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o42Eav0x020205 for ; Sun, 2 May 2010 14:36:57 GMT Message-ID: <27135225.5461272811017252.JavaMail.jira@thor> Date: Sun, 2 May 2010 10:36:57 -0400 (EDT) From: "Adam Kocoloski (JIRA)" To: dev@couchdb.apache.org Subject: [jira] Updated: (COUCHDB-753) Add config option for view compact dir In-Reply-To: <20555515.2191272756477295.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/COUCHDB-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Kocoloski updated COUCHDB-753: ----------------------------------- Hi Till, I'm having trouble figuring out how this would work. Are you saying you want to create the .compact file on another volume, then move it back to the volume hosting the view_index_dir when it's time to do the switchover? The trouble I see with that approach is that the final move of the compacted view index file would take a very long time. If the server crashed during the move, how would it know which file to choose? I guess one possible priority list might be 1) .view file in view_index_dir 2) .view.compact file in view_compact_dir 3) .view.compact file view_index_dir This would hopefully take care of the case where the .view file has been deleted but the server crashed before the .view.compact file could be completely transferred over to the original volume and renamed. > Add config option for view compact dir > -------------------------------------- > > Key: COUCHDB-753 > URL: https://issues.apache.org/jira/browse/COUCHDB-753 > Project: CouchDB > Issue Type: Improvement > Components: Database Core > Reporter: Till Klampaeckel > > CouchDB creates a "foo.view.compact" file in the view directory ("view_index_dir") when you run compact against a view. > I'd really like to be able to specify another directory where this ".compact" file is created and worked on. This is especially helpful when it's difficult to run compaction because you run out of disk space on the same device. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.