You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by "Coffman, Timothy A" <ti...@Vanderbilt.Edu> on 2009/10/26 15:50:51 UTC
Best practice for spreading one master across several disks?
I am collecting information and doing some proofs-of-concept in
preparation for suggesting CouchDB as a replacement for a 20-year-old
house-developed document system. One topic I will need to address goes
like this:
(1) How big can one CouchDB database file get?
(2) How could I store one CouchDB logical database across multiple disks
or machines?
Has anyone tried to address these?
Tim Coffman
Vanderbilt University Medical Center
(615) 936-6496
Re: Best practice for spreading one master across several disks?
Posted by Adam Kocoloski <ko...@apache.org>.
Yes, we'll certainly be integrating a distribution/sharding engine
into CouchDB core. Best,
Adam
On Oct 26, 2009, at 12:49 PM, AnotherNetFellow wrote:
> It seems an unofficial patch, isn't it?
>
> The CouchDB description states that it is a distributed db. So
> shouldn't it
> integrate a distribution engine to spare databases on many servers?
>
> Thankyou
>
> 2009/10/26 Adam Kocoloski <ko...@apache.org>
>
>> On Oct 26, 2009, at 10:50 AM, Coffman, Timothy A wrote:
>>
>> I am collecting information and doing some proofs-of-concept in
>>> preparation for suggesting CouchDB as a replacement for a 20-year-
>>> old
>>> house-developed document system. One topic I will need to address
>>> goes
>>> like this:
>>>
>>> (1) How big can one CouchDB database file get?
>>>
>>
>> Unlimited, although performance will get ugly once the indexes
>> don't fit in
>> RAM.
>>
>>
>> (2) How could I store one CouchDB logical database across multiple
>> disks
>>> or machines?
>>>
>>
>> Multiple disks: RAID
>>
>> Multiple machines: CouchDB-Lounge (not yet fully 0.10 compatible, but
>> they're working on it)
>>
>> http://tilgovi.github.com/couchdb-lounge/
>>
>> Best, Adam
>>
>>
>
>
> --
> --
> AnotherNetFellow
> Email: anothernetfellow@gmail.com
Re: Best practice for spreading one master across several disks?
Posted by AnotherNetFellow <an...@gmail.com>.
Oh, sorry Adam, I wasn't told you're one of project developers/managers.
Thankyou for your reply.
Jan: yes, it could be another type of use. It's, we could say, load
balancing. But think, and Adam seems confirming this, that another important
feature of non relational dbms is the ability to scale in size, without
limits (and a single server's capacity is a limit).
Giorgio
2009/10/26 Jan Lehnardt <ja...@apache.org>
>
> On 26 Oct 2009, at 17:49, AnotherNetFellow wrote:
>
> It seems an unofficial patch, isn't it?
>>
>
> couchdb-lounge is a full third party project on top of CouchDB, not a
> patch.
>
>
>
> The CouchDB description states that it is a distributed db. So shouldn't
>> it
>> integrate a distribution engine to spare databases on many servers?
>>
>
> There are different understandings of "distributed". CouchDB's idea is that
> distributing full data sets between nodes is an equally valid use-case (and
> IMHO a much more common one).
>
> That said, Adam already said CouchDB will have partitioning and it's
> a good thing :)
>
> Cheers
> Jan
> --
>
>
>
>
>
>> Thankyou
>>
>> 2009/10/26 Adam Kocoloski <ko...@apache.org>
>>
>> On Oct 26, 2009, at 10:50 AM, Coffman, Timothy A wrote:
>>>
>>> I am collecting information and doing some proofs-of-concept in
>>>
>>>> preparation for suggesting CouchDB as a replacement for a 20-year-old
>>>> house-developed document system. One topic I will need to address goes
>>>> like this:
>>>>
>>>> (1) How big can one CouchDB database file get?
>>>>
>>>>
>>> Unlimited, although performance will get ugly once the indexes don't fit
>>> in
>>> RAM.
>>>
>>>
>>> (2) How could I store one CouchDB logical database across multiple disks
>>>
>>>> or machines?
>>>>
>>>>
>>> Multiple disks: RAID
>>>
>>> Multiple machines: CouchDB-Lounge (not yet fully 0.10 compatible, but
>>> they're working on it)
>>>
>>> http://tilgovi.github.com/couchdb-lounge/
>>>
>>> Best, Adam
>>>
>>>
>>>
>>
>> --
>> --
>> AnotherNetFellow
>> Email: anothernetfellow@gmail.com
>>
>
>
--
--
AnotherNetFellow
Email: anothernetfellow@gmail.com
Re: Best practice for spreading one master across several disks?
Posted by Jan Lehnardt <ja...@apache.org>.
On 26 Oct 2009, at 17:49, AnotherNetFellow wrote:
> It seems an unofficial patch, isn't it?
couchdb-lounge is a full third party project on top of CouchDB, not a
patch.
> The CouchDB description states that it is a distributed db. So
> shouldn't it
> integrate a distribution engine to spare databases on many servers?
There are different understandings of "distributed". CouchDB's idea is
that
distributing full data sets between nodes is an equally valid use-case
(and
IMHO a much more common one).
That said, Adam already said CouchDB will have partitioning and it's
a good thing :)
Cheers
Jan
--
>
> Thankyou
>
> 2009/10/26 Adam Kocoloski <ko...@apache.org>
>
>> On Oct 26, 2009, at 10:50 AM, Coffman, Timothy A wrote:
>>
>> I am collecting information and doing some proofs-of-concept in
>>> preparation for suggesting CouchDB as a replacement for a 20-year-
>>> old
>>> house-developed document system. One topic I will need to address
>>> goes
>>> like this:
>>>
>>> (1) How big can one CouchDB database file get?
>>>
>>
>> Unlimited, although performance will get ugly once the indexes
>> don't fit in
>> RAM.
>>
>>
>> (2) How could I store one CouchDB logical database across multiple
>> disks
>>> or machines?
>>>
>>
>> Multiple disks: RAID
>>
>> Multiple machines: CouchDB-Lounge (not yet fully 0.10 compatible, but
>> they're working on it)
>>
>> http://tilgovi.github.com/couchdb-lounge/
>>
>> Best, Adam
>>
>>
>
>
> --
> --
> AnotherNetFellow
> Email: anothernetfellow@gmail.com
Re: Best practice for spreading one master across several disks?
Posted by AnotherNetFellow <an...@gmail.com>.
It seems an unofficial patch, isn't it?
The CouchDB description states that it is a distributed db. So shouldn't it
integrate a distribution engine to spare databases on many servers?
Thankyou
2009/10/26 Adam Kocoloski <ko...@apache.org>
> On Oct 26, 2009, at 10:50 AM, Coffman, Timothy A wrote:
>
> I am collecting information and doing some proofs-of-concept in
>> preparation for suggesting CouchDB as a replacement for a 20-year-old
>> house-developed document system. One topic I will need to address goes
>> like this:
>>
>> (1) How big can one CouchDB database file get?
>>
>
> Unlimited, although performance will get ugly once the indexes don't fit in
> RAM.
>
>
> (2) How could I store one CouchDB logical database across multiple disks
>> or machines?
>>
>
> Multiple disks: RAID
>
> Multiple machines: CouchDB-Lounge (not yet fully 0.10 compatible, but
> they're working on it)
>
> http://tilgovi.github.com/couchdb-lounge/
>
> Best, Adam
>
>
--
--
AnotherNetFellow
Email: anothernetfellow@gmail.com
Re: Best practice for spreading one master across several disks?
Posted by Adam Kocoloski <ko...@apache.org>.
On Oct 26, 2009, at 10:50 AM, Coffman, Timothy A wrote:
> I am collecting information and doing some proofs-of-concept in
> preparation for suggesting CouchDB as a replacement for a 20-year-old
> house-developed document system. One topic I will need to address
> goes
> like this:
>
> (1) How big can one CouchDB database file get?
Unlimited, although performance will get ugly once the indexes don't
fit in RAM.
> (2) How could I store one CouchDB logical database across multiple
> disks
> or machines?
Multiple disks: RAID
Multiple machines: CouchDB-Lounge (not yet fully 0.10 compatible, but
they're working on it)
http://tilgovi.github.com/couchdb-lounge/
Best, Adam