You may have run out of inodes, or inodes limit is being reached. I've seen
this before. Just something to check, not saying it is the issue. Given how
many resources you are handling, this is the first thing that came to mind.
Wendall
On Mon, Jul 25, 2022 at 8:36 AM Josh Kuestersteffen
wrote:
You're running into the couchjs stack size limit, and the process is
being killed. The message is a little obscure, but this can happen with
large JSON docs. There is a good answer left by Kxepal here:
http://stackoverflow.com/questions/21273736/couchdb-views-os-process-error-big-documents
on h
Are you updating the same doc 10k times? Or writing a new doc each time?
If it's the former, this isn't a really good test for CouchDB, and
certainly going to be slow.
Wendall
On 04/03/2014 07:40 PM, Knudsen, Ken wrote:
to a CouchDB serverI'm literally just executing a unit test 10k t
A new book was released by O'Reilly last month called Speaking
JavaScript. The book is avaliable for free online at
http://speakingjs.com . The book references CouchDB in a couple places,
most interestingly in an excerpt from the chapter "Historical JavaScript
Milestones". http://speakingjs.com
The patch looked good. I'll merge this in the very near future. Thanks
for reporting this and lending a hand!
Wendall
On 05/14/2013 10:08 PM, Anishek Agarwal wrote:
I think one of my colleagues has submitted a patch for this with the
stop_couch() function change. We will know soon if that will
On 05/14/2013 11:05 AM, Noah Slater wrote:
On 14 May 2013 13:19, Anishek Agarwal wrote:
Note: Support for apache couchdb 1.2.x is not provided by Apache foundation
anymore right ?
Yep! But the upgrade path from 1.2.x is to 1.3.x. :)
This PID file bug is annoying. Would be a great opportunit
On 05/09/2013 05:52 AM, svilen wrote:
The main concern I have is maintaining a consistent state across
code releases. Presumably, our data model will change over the
course of time, and when it does, we need to make the several
million old documents conform to the new model.
a question: do u ne
I agree with this approach. I do something similar using _sum:
emit([doc.country_name, toDay(doc.timestamp)], 1);
The toDay() method is basically a floor of the day value. Since I don't
store ts in UTC (Because of an idiotic error some years back) I also do
a tz offset to correct the day value
Just a thought here. Can you check if you have any IO issues or are out
of drive space on the machine throwing the errors?
Wendall
On 03/22/2013 07:52 AM, Gerald Richter - ECOS wrote:
[<<"index">>],<<"\\&CouchDB::AppServ::
Docclass::map_doctype #version=19">>,
doesn't look quite right to me.
The performance of a write per read in updating the doc with a timestamp
would be very, very poor in CouchDB.
The best scenario is create a separate stats database. Every time a doc
in the database you are tracking for is accessed, create a doc
describing the request in a stats database. Creat
We use couchdb in two configurations.
1. As a couchapp serving content for basic consumption. (For a url
shortener service)
2. As a database on localhost behind pylons or pyramid.
To address the security question. We've been using couchdb for long
enough that it didn't have any security when
leverage arrays for creating view indexes will change how you use
CouchDB (for the better).
Wendall
On 02/22/2013 01:13 PM, Wendall Cada wrote:
I wanted to give my feedback about what I've learned in this area.
First, I don't use the doc _id at all for sorting docs. It solves one
I wanted to give my feedback about what I've learned in this area.
First, I don't use the doc _id at all for sorting docs. It solves one
single use-case, but fails if you have others, so instead, I do this:
Every doc, whether the parent or child has identifying information. So a
child might c
I created an rpm spec for 1.2.0 and instructions for building
spidermonkey 1.8.5 https://github.com/wendall911/couchdb-rpm. We
currently use this in production on Amazon Linux. Build the rpms. Update
spidermonkey. Install couchdb. Done.
Wendall
On 09/01/2012 05:14 AM, Martin Hewitt wrote:
Hi
Like I said there are some features actually missing in couch that
would ease that. (partial updates and partial fetch). Of course a view
could be use to see only profile but that would be a hack.
And this is not only about being a db or something alternative. This
is more about security here.
place a third party authentication system
with CouchDB except for the most simplistic situations possible.
Wendall
B.
On 30 Aug 2012, at 19:38, Wendall Cada wrote:
An example of this is a comments thread moderator. They need permissions to
edit portions of a doc that doesn't belong to them. Is it proposed that I just
make everyone an admin?
Jim,
This is a very well thought out response. I believe is correct. In the
current state, _users is unusable for anything other than 1. I don't
even bother with that since I have to create an app layer to actually
manage permissions, so I just don't expose it externally and run admin
party a
ve added a
V6 engine to the installing scripts. ;)
If you have problems, don't hesitate to post them here. I will help with
what I can.
Cheers,
CGS
On Thu, May 31, 2012 at 11:51 PM, Wendall Cada wrote:
George,
Can you share your build instructions? If you have a working install
proce
George,
Can you share your build instructions? If you have a working install
process for Centos 5.8, I can create an rpm that could benefit others.
5.8 is problematic. I think the information could be very useful for
build-couchdb as well, as I think it isn't working currently either.
Wendal
This appears to be an ESX Hypervisor crash. CouchDB doesn't do anything
that any other app can do in terms of crashing your hypervisor. Probably
a VMWare bug, so check your host server logs and see if you can isolate
what is causing the crash. IMO, this has nothing whatsoever to do with
CouchDB
I've created a working spec file and patches that match what's available
in Fedora (couchdb-1.0.3) and Centos (couchdb-1.0.2), but for 1.2.0-git.
I've added a patch for COUCHDB-1424 provided by Filipe. I'll pull this
patch out once 1.2.0 is ready for a vote again and other changes have
been pus
It would be really incredibly if you blogged about this, or shared
your setup with the rest of us. :)
Wendall
On 07/15/2010 06:34 PM, J Chris Anderson wrote:
On Jul 15, 2010, at 5:22 PM, Chris Stockton wrote:
Now I am happily replicating a few thousand db's.
Music to my ears! Glad you go t
I recently had an issue with my mail server. It appears as though this
suspended email being sent to my email address. Since there appears to
be no user interface for managing mailing list accounts, and the server
is ignoring any subscribe/unsubscribe request, I'm sending this email as
a last d
On 06/30/2010 04:54 PM, cdr53x wrote:
Hi,
Maybe the wiki page should mention that the
/etc/ld.so.conf.d/xulrunner.conf file must be manually changed
whenever the xulrunner libs are updated ... ( for instance in the
yesterday's ubuntu 10.04 update )
I know it seems obvious, but we're so use
I think the only issue is with libcurl. I built curl-7.20.1 locally and
compiled against those libs. 0.11.0 built fine for me then.
HTH,
Wendall
On 06/29/2010 11:43 AM, Rob Dean wrote:
I'm arriving late on a project where there is a current proposal to use
CouchDB. Although this is OK from a
On 06/29/2010 06:51 AM, Dirkjan Ochtman wrote:
On Tue, Jun 29, 2010 at 15:32, Wendall Cada wrote:
While doing some preliminary research on building a couchdb rpm, I
discovered that Fedora/Centos/RedHat couchdb rpms are built against
js-devel-0.70.
You mean 1.7.0?
Yes, the
js-0.70. Maybe OSX has a habit of reporting incorrect
versions, but I've not seen any core maintained packages with anything
bit minor rev discrepancies. The spec file says that it is built against
this.
On 29.06.2010, at 15:32, Wendall Cada wrote:
While doing some preliminary resear
While doing some preliminary research on building a couchdb rpm, I
discovered that Fedora/Centos/RedHat couchdb rpms are built against
js-devel-0.70.
As can be seen here:
$ js -v
JavaScript-C 1.7.0 2007-10-03
I am quite shocked that it is being built against something so ancient.
xulrunner-de
RHEL really only supports fairly old software in general. For anything
bleeding edge or current, you'll need to build your own rpms, or find a
well maintained repo. You can use the srpm for curl to build an updated
package. However, libcurl.so.3 is going to be hard to work around with
those sol
On 06/09/2010 12:23 PM, Phat Loc wrote:
Hi All,
I am new to Javascript and Couchdb. What tools do you use to create
design docs or JavaScript? I am not a web page developer so I am
looking for a JavaScript repl. Futon is very difficult to use for
creating list in design docs.
I recommend Ja
30 matches
Mail list logo
