On Fri, Sep 21, 2012 at 2:05 AM, aaron morton aa...@thelastpickle.com wrote:
Would it help if I partitioned the computing resources of my physical
machines into VMs?
No.
Just like cutting a cake into smaller pieces does not mean you can eat more
without getting fat.
In the general case,
Would it help if I partitioned the computing resources of my physical
machines into VMs?
No.
Just like cutting a cake into smaller pieces does not mean you can eat more
without getting fat.
In the general case, regular HDD and 1 Gbe and 8 to 16 virtual cores and 8GB to
16GB ram, you can
Given the advice to use a single RAID 0 volume, I think that's what I'll do.
By system mirror, you are referring to the volume on which the OS is
installed?
Yes.
I was thinking about a simple RAID 1 OS volume and RAID 0 data volume setup.
With the Commit Log on the OS volume so it does
On Tue, Sep 18, 2012 at 1:54 AM, aaron morton aa...@thelastpickle.comwrote:
each with several disks having large capacity, totaling 10 - 12 TB. Is
this (another) bad idea?
Yes. Very bad.
If you had 6TB on average system with spinning disks you would measure
duration of repairs and
Network also matters. It would take a lot of time sending 6TB over 1Gb
link, even fully saturating it. IMHO You can try with 10Gb, but you will
need to raise your streaming/compaction limits a lot.
Also you will need to ensure that your compaction can keep up. It is often
done in one thread and I
4 drives for data and 1 drive for commitlog,
How are you configuring the drives ? It's normally best to present one big data
volume, e.g. using raid 0, and put the commit log on say the system mirror.
will the node balance out the load on the drives, or is it agnostic to usage
of drives
A word of warning. If you put more than 300GB to 400GB per node you may
end experience some issues ...
I think this is probably the solution to your multiple disk problem. You
could use easily one single disk to store the data on, and one disk for the
commitlog. No issues with JBOD, RAID or
On Mon, Sep 17, 2012 at 1:19 AM, aaron morton aa...@thelastpickle.comwrote:
4 drives for data and 1 drive for commitlog,
How are you configuring the drives ? It's normally best to present one big
data volume, e.g. using raid 0, and put the commit log on say the system
mirror.
Given the
I'm building a new cluster (to replace the broken setup I've written
about in previous posts) that will consist of only two nodes. I understand
that I'll be sacrificing high availability of writes if one of the nodes
goes down, and I'm okay with that. I'm more interested in maintaining high
