couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1592) Free space check for automatic compaction doesn't follow symlinks
Date Wed, 07 Nov 2012 13:41:12 GMT

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

Robert Newson commented on COUCHDB-1592:
----------------------------------------

No, it couldn't, because databases are held open. You don't change storage devices out from
under database servers. The kind of live upgrade I think Benoit is referring to is not yet
possible with couchdb, until we get the whole OTP release thing going.

As for this ticket, I see a simple enough fix to use the capacity of the device pointed at
by the symlink, and it's obviously the better answer. The only caveat I have is that disksup
is buggy (issues with some paths, it won't work on OS X correctly, for example). Since the
compaction daemon is optional, I don't think it's blocking a fix here.
                
> Free space check for automatic compaction doesn't follow symlinks
> -----------------------------------------------------------------
>
>                 Key: COUCHDB-1592
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1592
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Nils Breunese
>
> We've got a problem with automatic compaction not running due to low diskspace according
to CouchDB. According to our system administrators there is more than enough space (more than
twice the currently used space), but the data directory is a symlink to the real data storage.
It seems CouchDB is checking the diskspace on the filesystem on which the symlink resides
instead of the diskspace on the linked filesystem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message