Re: Couchdb 1.3 Mac OS X version crashes after 25836 doc updating

Hi, Basically, the error says that the call to the gen_server process with pid 0.28246.0 didn't returned any result in 5 seconds when processing that message. This indicates that some resource is very busy, may be the view engine. Best Regards, Bogdan On Wed, Apr 17, 2013 at 6:50 AM, Gennady

CouchDB: 2.0 & 1.6.1 database compatibility

Hello, I configured a single-node CouchDB 2.0 instance and I copied in data directory 1.6.1 couch databases. But the databases does not show up in Fauxton, only the test databases: ["_global_changes","_replicator","_users","verifytestdb"]. Is there a way to make CouchDB 2.0 read 1.6.1 couch

Re: CouchDB: 2.0 & 1.6.1 database compatibility

-cases for each one of the query methods? Thanks, Bogdan On Fri, Oct 7, 2016 at 11:20 AM, max <maxima...@gmail.com> wrote: > Hi, > > Install 2.0 version on another server or just make it listen on different > port than 1.6 then replicate your data ;) > > 2016-10-07 9:49 GM

Re: CouchDB: 2.0 & 1.6.1 database compatibility

replication is always smaller. > This is due to previous documents revisions remaining in source db but not > send to target during replication. > > Max > > 2016-10-07 11:29 GMT+02:00 Bogdan Andu <bog...@gmail.com>: > > > I see the data management is totally differe

Re: Couchdb 2.0 installation issue - missing _users

u need to do these: curl -X PUT http://10.10.13.104:5984/_users curl -X PUT http://10.10.13.104:5984/_replicator curl -X PUT http://10.10.13.104:5984/_global_changes /Bogdan On Fri, Oct 7, 2016 at 12:51 PM, Garren Smith wrote: > Hi Karl, > > You need to setup the cluster

Re: CouchDB: 2.0 & 1.6.1 database compatibility

to have multiple storage engines that follow the same replication protocol, of course /Bogdan On Mon, Oct 10, 2016 at 3:21 PM, Jan Lehnardt <j...@apache.org> wrote: > > > On 10 Oct 2016, at 12:42, Bogdan Andu <bog...@gmail.com> wrote: > > > > but still doe

Re: Problem during installation of couchdb-2.0 on CentOS 6.

Python (>=2.7) for docs (http://python.org/) > * Python Sphinx (>=1.1.3)(http://pypi.python.org/pypi/Sphinx) > > None of them required to be build against erlang, only couchdb fill full > this requirement. > Then when you to recompile everything, what i'm suppose to under

Re: Problem during installation of couchdb-2.0 on CentOS 6.

recompile everything with new erlang On Thu, Sep 29, 2016 at 10:41 AM, Yacine El Ayar wrote: > Ok i've review the installation of erlang (before i've not used make > install but update PATH and LD_LIBRARY_PATH to tell the os to point to the > latest version of erlang).

Re: CouchDB 2.0 start/stop dilemma

server with: $ sudo systemctl start couchdb20 $ sudo systemctl stop couchdb20 or see the status: $ sudo systemctl status couchdb20 /Bogdan On Wed, Oct 12, 2016 at 1:14 PM, Bogdan Andu <bog...@gmail.com> wrote: > Hi, > > I see Couch 2.0 comes with a free style start / stop m

CouchDB 2.0 start/stop dilemma

Hi, I see Couch 2.0 comes with a free style start / stop mechanism and the user is encouraged to use runit or whatever mechanism he already has on his system. I do not want to use runit when I have modern systems like centos 7 or f edora 24 server editions that have systemd to start/stop couchdb

Re: CouchDB: 2.0 & 1.6.1 database compatibility

On Mon, Oct 10, 2016 at 4:36 PM, Jan Lehnardt <j...@apache.org> wrote: > > > On 10 Oct 2016, at 14:59, Bogdan Andu <bog...@gmail.com> wrote: > > > > yes, I know , but couchdb storage engine cannot optimize > > this while operating normaly. only after c

Re: CouchDB: 2.0 & 1.6.1 database compatibility

org> wrote: > > > On 10 Oct 2016, at 11:54, Bogdan Andu <bog...@gmail.com> wrote: > > > > Hi, > > > > I return with updated info : > > > > I compacted db1 (CouchDB/1.6.1) on the source and now has 350 MB from > 2.5 GB > > with 362849

Re: CouchDB: 2.0 & 1.6.1 database compatibility

ript roundtrip. Querying performance should > be ~identical. Cheers, > > Adam > > > On Oct 7, 2016, at 7:56 AM, Thanos Vassilakis <than...@gmail.com> wrote: > > > > Good questions > > > > Sent from my iPhone > > > >> On Oct 7, 2016, at 5: