Date: Wed, 15 Aug 2012 12:18:39 -0700 (PDT)
From: maibeck <nicholasbec...@gmail.com>
To: bigcouch-user@googlegroups.com
Message-Id: <6ad80936-9e90-4af0-86cf-d24b79f14ab7@googlegroups.com>
In-Reply-To: <ffdbcec4-9d59-478a-aeb9-99f28fca73fa@googlegroups.com>
References: <7c16c178-5b4d-489f-97ad-c32e52fa85ac@googlegroups.com>
 <bc5a2b31-9681-4786-af51-a0d0deae1b5d@googlegroups.com>
 <ffdbcec4-9d59-478a-aeb9-99f28fca73fa@googlegroups.com>
Subject: Re: Production usage of BigCouch and the Future?
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1087_2875106.1345058319591"

------=_Part_1087_2875106.1345058319591
Content-Type: multipart/alternative; 
	boundary="----=_Part_1088_3540503.1345058319591"

------=_Part_1088_3540503.1345058319591
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I posted the issue on github, but haven't heard back.  
https://github.com/cloudant/bigcouch/issues/111


On Wednesday, August 15, 2012 11:33:01 AM UTC-6, Behrad Zari wrote:
>
> Oh, Thank you Maibeck for your feekback! 
> Have they confirmed those issues or they are for your case of 
> configuration!?
>
>
> On Wednesday, August 15, 2012 6:32:55 PM UTC+4:30, maibeck wrote:
>>
>> I cannot recommend going to production using the current release (0.4.0). 
>>  There are still some major bugs that need to be addressed in order to 
>> create a stable environment ready for production.  
>>
>> The biggest issue for us was that views would often need to be rebuilt 
>> from scratch.  View generation can take hours/days to complete with large 
>> data sets, which in a couple cases took down our applications for days at a 
>> time.  We weren't ever able to consistently repeat the behavior, but it 
>> seemed to occur under high load, or after the server/service was restarted.
>>
>> Cloudant's hosted platform appears to be quite stable, and has some 
>> additional features not found in bigcouch, namely chained map-reduce. 
>>  I would recommend using Cloudant if you're considering taking the bigcouch 
>> path.
>>
>>
>> On Tuesday, August 14, 2012 8:18:37 AM UTC-6, Behrad Zari wrote:
>>>
>>> Howdy Big! Couchers,
>>>
>>> We are estimating to deal with large-scale couchdb views (about more 
>>> than hundred Gigs of couchdb indexes) in production.
>>> (Which I don't think is a feasible size on a single couchdb on one 
>>> machine, because of limited machine memory !?)
>>> To provide index partitioning, we are thinking of BigCouch, which is 
>>> lovely fork of Couchdb, but I'm not sure about the future!?
>>> I've read links but have not found any roadmap or planned merge! Since 
>>> we are planing for a critical system in production, I wonder
>>> if using BigCouch will be risky or not?
>>>
>>> Thank you in advance,
>>>
>>
------=_Part_1088_3540503.1345058319591
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

I posted the issue on github, but haven't heard back. &nbsp;<a href=3D"http=
s://github.com/cloudant/bigcouch/issues/111">https://github.com/cloudant/bi=
gcouch/issues/111</a><div><br></div><div><br>On Wednesday, August 15, 2012 =
11:33:01 AM UTC-6, Behrad Zari wrote:<blockquote class=3D"gmail_quote" styl=
e=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left:=
 1ex;">Oh, Thank you Maibeck for your feekback!&nbsp;<div>Have they confirm=
ed those issues or they are for your case of configuration!?<div><br><br>On=
 Wednesday, August 15, 2012 6:32:55 PM UTC+4:30, maibeck wrote:<blockquote =
class=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;border-left:1px #=
ccc solid;padding-left:1ex">I cannot recommend going to production using th=
e current release (0.4.0). &nbsp;There are still some major bugs that need =
to be addressed in order to create a stable environment ready for productio=
n. &nbsp;<div><br></div><div>The biggest issue for us was that views would =
often need to be rebuilt from scratch. &nbsp;View generation can take hours=
/days to complete with large data sets, which in a couple cases took down o=
ur applications for days at a time. &nbsp;We weren't ever able to consisten=
tly repeat the behavior, but it seemed to occur under high load, or after t=
he server/service was restarted.<div><div><div><br></div><div>Cloudant's ho=
sted platform appears to be quite stable, and has some additional features =
not found in bigcouch, namely chained map-reduce. &nbsp;I&nbsp;would recomm=
end using Cloudant if you're considering taking the bigcouch path.</div><di=
v><br></div><div><br>On Tuesday, August 14, 2012 8:18:37 AM UTC-6, Behrad Z=
ari wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0;margin-left:0=
.8ex;border-left:1px #ccc solid;padding-left:1ex">Howdy Big! Couchers,<div>=
<br><div>We are estimating to deal with large-scale couchdb views (about mo=
re than hundred Gigs of couchdb indexes) in production.</div><div>(Which I =
don't think is a feasible size on a single couchdb on one machine, because =
of limited machine memory !?)</div><div>To provide index partitioning, we a=
re thinking of BigCouch, which is lovely fork of Couchdb, but I'm not sure =
about the future!?</div><div>I've read links but have not found any roadmap=
 or planned merge! Since we are planing for a critical system in production=
, I wonder</div><div>if using BigCouch will be risky or not?</div><div><br>=
</div><div>Thank you in advance,</div></div></blockquote></div></div></div>=
</div></blockquote></div></div></blockquote></div>
------=_Part_1088_3540503.1345058319591--

------=_Part_1087_2875106.1345058319591--