Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAOhzf+WfL-bN9KttyFriuO7O3Cbtjd-1Y+E3ZR+AG4fAKyXs+A@mail.gmail.com>
References: 
 <CAOhzf+XG6zi30MhC3pKoJkDAK752BCJrzo_3J3_TyqMyb6o5Ww@mail.gmail.com>
	<CABvT1DH2TYMbWu6ZYC7u3g89tUDZffooh1WAiDH0gUsnTpBUag@mail.gmail.com>
	<CAOhzf+WfL-bN9KttyFriuO7O3Cbtjd-1Y+E3ZR+AG4fAKyXs+A@mail.gmail.com>
Date: Sat, 16 Nov 2013 17:04:32 +0000
Message-ID: 
 <CABvT1DGQff8ZL6pG=OcEz6dFLmkcNWMBvuR8tW+p579EWeX9aQ@mail.gmail.com>
Subject: Re: Couch crashing under medium load
From: Robert Newson <rnewson@apache.org>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

eaddrinuse means that couchdb can't bind to the 5984 port. Perhaps you
have two couchdb's attempting to run at once?

B.


On 16 November 2013 16:59, Joe RNL <jmorgan@rednovalabs.com> wrote:
> OS: Ubuntu 12.04
> Server : m1.xlarge amazon (but have tried on other sizes with no success)
> Couchdb Version: 1.2.0
> Crash Report:
>
> [Fri, 15 Nov 2013 22:30:51 GMT] [error] [<0.124.0>] {error_report,<0.30.0>,
>                         {<0.124.0>,crash_report,
>                          [[{initial_call,
>
>  {mochiweb_socket_server,init,['Argument__1']}},
>                            {pid,<0.124.0>},
>                            {registered_name,[]},
>                            {error_info,
>                                {exit,eaddrinuse,
>                                    [{gen_server,init_it,6},
>                                     {proc_lib,init_p_do_apply,3}]}},
>                            {ancestors,
>                                [couch_secondary_services,couch_server_sup,
>                                 <0.31.0>]},
>                            {messages,[]},
>                            {links,[<0.93.0>]},
>                            {dictionary,[]},
>                            {trap_exit,true},
>                            {status,running},
>                            {heap_size,1597},
>                            {stack_size,24},
>                            {reductions,455}],
>                           []]}}
> erlang: 5.8.5
> spidermonkey: 1.9.1.15-2ppa0+1
>
> Siege command :
> siege -c 80 -i -d 1 URL
> Typical response:
>
> Transactions:         562 hits
> Availability:       77.95 %
> Elapsed time:       43.96 secs
> Data transferred:        2.99 MB
> Response time:        4.85 secs
> Transaction rate:       12.78 trans/sec
> Throughput:        0.07 MB/sec
> Concurrency:       61.97
> Successful transactions:         721
> Failed transactions:         159
> Longest transaction:       14.01
> Shortest transaction:        0.01
>
> Trying with 20-40 concurrent users is fine.
> Tweaks: I've tried everything listed in this document:
> http://wiki.apache.org/couchdb/Performance
>
> Using htop I can see the memory usage slowly climb before couchdb crashes.
> Usually around 3000 available of 14980MB available.
>
> Thanks
>
> joe
>
>
> On Sat, Nov 16, 2013 at 7:33 AM, Robert Newson <rnewson@apache.org> wrote:
>
>> There's no detail here for us to even begin to help. What OS, machine
>> specs, version of couchdb, erlang, spidermonkey, what is "medium
>> load"? which tweaks have you made? What were the crashes (See
>> couch.log)?
>>
>> B.
>>
>>
>> On 16 November 2013 13:26, Joe RNL <jmorgan@rednovalabs.com> wrote:
>> > Apologies if double post. We are testing a new system architecture and
>> > couch keeps crash under relatively light loads, about 40 concurrent
>> > requests.
>> >
>> > Any thoughts?
>> >
>> > What I've tried:
>> > - Tweaking settings
>> > http://wiki.apache.org/couchdb/Performan<
>> http://wiki.apache.org/couchdb/Performance>
>> > - Testing with both Siege and AB
>> > - Tried different cloud-based servers.
>> >
>> > Doesn't seem to be a memory issue, as there is always plenty of available
>> > memory.
>> >
>> > thanks
>> >
>> > joe
>>