Re: CouchDB 2.0 as Snap

[Dave Cottlehuber]

> However at present they have a serious limitation wrt storage that is a
> production showstopper - each snap version creates a new copy of
> couchdb, and copies across the data files. I can't confirm yet if this

BTW damjan on IRC pointed out SNAP_COMMON: writable area persistent
across all revisions of the snap at
http://snapcraft.io/docs/reference/env  which if suitable would be
great.

A+
Dave

[NEWS] The CouchDB weekly news for September 22 is out!

[Jenn Turner]

Hello there!

  

The CouchDB weekly news is now live at: https://blog.couchdb.org/2016/09/22
/couchdb-weekly-news-september-22-2016/

  

Highlights include press coverage of the CouchDB version 2.0 release this
week, lots of new releases for PouchDB, plus Henry Rollins like you probably
have not seen!

  

Great work this week everyone! :D :D :D

  

You can help us spread the news by sharing on Twitter
(https://twitter.com/CouchDB/status/778957834197331968) and other social
networks.  

  

Also, **if you have news for next week**, just REPLY to this thread!

  

Cheers!  
  

Jenn Turner

The Neighbourhoodie Software GmbH  
Adalbertstr. 7-8, 10999 Berlin  
[neighbourhood.ie](http://neighbourhood.ie/)  
  

Handelsregister HRB 157851 B Amtsgericht Charlottenburg  
Geschäftsführung: Jan Lehnardt

Re: CouchDB 2.0 as Snap

[Dave Cottlehuber]

> >>> On Mon, Sep 19, 2016 at 4:47 AM, Michael Hall  
> >>> wrote:
> >>> 
> >>> First off, congratulations on the upcoming 2.0 release!
> >>> 
> >>> I would love to see this new version available as a Snap package for
> >>> users of Ubuntu 16.04 LTS, since the archive version will be frozen on

Thanks Michael,

These sound awesome. Snaps are looking great -- especially compared to
the frustration of older debian / centos packaging tools that carry 2
decades of cruft under the hood.

However at present they have a serious limitation wrt storage that is a
production showstopper - each snap version creates a new copy of
couchdb, and copies across the data files. I can't confirm yet if this
is copy-on-write or not which at least would not be (initially) too bad,
or a naive copy that duplicate disk blocks entirely. I suspect the
latter as there is not much choice when it comes to cross-filesystem
compatibility. Either way, if you have reasonably sized couches & viewed
snaps will put you in a situation of needing to clean up old data to
avoid running out of free disk space (e.g. during compaction) due to
data kept in old snaps.

We're not the only database to experience this constraint however and
I'm sure a suitable solution will appear in due course. Go snaps!

A+
Dave