Re: Do not save tables in ram?

Matthew,

Ok so we have to keep adding more data files as the end of tablespace is reached.

Last 2 questions... When creating tablespaces. data files, log files, etc, are they automatically replicated on each data node or must you create them each individually on each node or do they only live on the node they are created?

... And lastly, is there something out there to warn you when your usage is almost up so you can add more data files etc so your cluster does not fail when users are trying to input data?

Thank you,
- Jake

On 10/1/07, Matthew Montgomery <mmontgomery@mysql.com> wrote:
> On Mon, 2007-10-01 at 15:28 -0700, Jake Conk wrote:
> > Matthew,
> >
> > Nice, this is exactly what I was looking for but I have a few minor
> > questions.
> >
> > 1) When creating disk data objects what's the point of creating an
> > initial size? Does this initial size matter and 1.a) what happens if
> > the inputted in the table exceeds the initial size? It should just
> > keep going right?
>
> See: http://dev.mysql.com/doc/refman/5.1/en/create-tablespace.html
>
> The INITIAL_SIZE parameter sets the data file's total size in bytes.
> Once the file has been created, its size cannot be changed; however, you
> can add more data files to the tablespace using ALTER TABLESPACE ... ADD
> DATAFILE.
>
> INITIAL_SIZE is optional; its default value is 128M.
>
> AUTOEXTEND_SIZE, MAX_SIZE, NODEGROUP, WAIT, and COMMENT are parsed but
> ignored, and so have no effect in MySQL 5.1. These options are intended
> for future expansion.
>
> Currently the table will return:
> ERROR 1114 (HY000): The table 'tbl_name' is full
>
> > 2) Is the DataMemory effected by Disk Data Objects? So say if my
> > DataMemory is set to 1gb and I'm using 900mb of space with my disk
> > data objects then once I reach 1gb with my disk data objects then I
> > will have to change my DataMemory to a larger number or is the size of
> > my disk data objects completely unrelative and would just keep on
> > growing until I pretty much run out of disk space?
>
> DataMemory usage will grow along with the volume of in-memory columns in
> the table. There will always be an in-memory component of the table for
> the primary key and any indexed columns.
>
> DataMemory usage unrelated to usage in a tablespace datafile.
>
> --
> Matthew Montgomery, Support Engineer
> San Antonio, TX
> MySQL Inc, www.mysql.com
>
>

-- 
MySQL Cluster Mailing List
For list archives: 
http://lists.mysql.com/cluster
To unsubscribe:    
http://lists.mysql.com/cluster?unsub=lists@pantek.com