In the end the errors ended up (ironically) being caused by a bad call to
our error monitoring service. We run couchdb behind a rails proxy and we
were randomly seeing 500 errors on some proxy requests with no backtrace so
it was hard to track down.
Benoit, by graceful I mean something like unico
We were running into issues with our couchdb server today and ended up
restarting couchdb after exhausting other options.
I'm curious -- are couchdb restarts graceful? Or are all current requests
immediately terminated?
Thanks
-Ryan
For a while now I've wished couchdb had a fork feature to speed up initial
replication times like this.
curl -X POST -d '{"source":"db1","target":"db2"}'
http://localhost:5984/_fork
Basic process would be something like:
1. Do a simple file system copy to create the new db
2. Set the replication
> Well I am not sure you want a documented oriented database then ;) Imo
you are thinking to an object database :)
As far as my needs go there's no difference between the two. Everything I
store in CouchDB is just an object anyway.
If it helps shed some context, here are the primary reasons I ch
The show/list thread (posted by thomas.b...@ptb.de) recently sparked an
interesting debate. Like Joan, I too feel that CouchDB tries to handle way
more than it should. (Caveat -- I actually take this stance to the extreme
believing that the couchapp behavior and utilities like futon/fauxton
should
Of course it is, but Alex asked can I not should I.
Dave, this isn't my thread. Alex had asked:
> Is there any way to unconditionally overwrite a document without
first making a round-trip to get the current rev?
Everyone said no. Looks like it's totally doable using new_edits=false and
a script that resolves any conflicts by simply picking the mo
Jens - Can you expand on this more or point me to documentation that covers
this in detail?
On Friday, November 8, 2013, Jens Alfke wrote:
>
>
> This would add a new revision, but it'd be a new roots in the revision
> tree (i.e. a sibling not a child of the previous revision.) This would
> essenti
Couldn't you do this with _bulk_docs and new_edits:false?
http://wiki.apache.org/couchdb/HTTP_Bulk_Document_API#Posting_Existing_Revisions
>From the readme:
> PouchDB uses various backends so it can work across various browsers and
in Node.js. It uses IndexedDB in Firefox and Chrome, WebSQL in Safari and
Opera and LevelDB in Node.js
https://github.com/daleharvey/pouchdb
On Wed, Nov 6, 2013 at 4:15 PM, Jens Alfke wrote:
>
> On No
That's essentially what PouchDB has done, yeah?
On Tue, Nov 5, 2013 at 11:13 AM, Jim Klo wrote:
>
> On Nov 5, 2013, at 11:08 AM, Ryan Mohr
> wrote:
>
> > Rethink caught my interest a little while back too. Looks like a well
> > designed database and a great coll
Rethink caught my interest a little while back too. Looks like a well
designed database and a great collection of tools to support it.
The immediate difference that jumped out at me (and the ultimate reason I
chose couch over rethink) is that rethink does not and will never support
master-master
derstood right that the request chain is user -> rails ->
excon -> couchdb ?
--
,,,^..^,,,
On Thu, Oct 31, 2013 at 12:39 AM, Ryan Mohr wrote:
> Lately I've been running into an annoying bug where requests are silently
> being dropped. They're logged at the debug level and
Lately I've been running into an annoying bug where requests are silently
being dropped. They're logged at the debug level and then nothing happens.
No error and no info level confirmation that the request went through.
This only seems to happen with PUT/POST requests and only once the
connectio
14 matches
Mail list logo
