14 messages in com.mysql.lists.clusterRe: DataMemory Strange Behaviour| From | Sent On | Attachments |
|---|---|---|
| Adam Dixon | 24 Jul 2005 20:20 | |
| Mikael Ronström | 25 Jul 2005 01:34 | |
| Matthew Glubb | 25 Jul 2005 01:46 | |
| Mikael Ronström | 25 Jul 2005 01:59 | |
| Matthew Glubb | 25 Jul 2005 02:12 | |
| Adam Dixon | 25 Jul 2005 03:09 | |
| Mikael Ronström | 25 Jul 2005 03:17 | |
| Matthew Glubb | 25 Jul 2005 03:20 | |
| Matthew Glubb | 25 Jul 2005 03:40 | |
| Jonas Oreland | 25 Jul 2005 03:54 | |
| Mikael Ronström | 25 Jul 2005 04:36 | |
| Adam Dixon | 25 Jul 2005 05:11 | |
| Mikael Ronström | 25 Jul 2005 05:52 | |
| Adam Dixon | 25 Jul 2005 06:14 |
| Subject: | Re: DataMemory Strange Behaviour |
|---|---|
| From: | Adam Dixon (adam...@gmail.com) |
| Date: | 07/25/2005 05:11:56 AM |
| List: | com.mysql.lists.cluster |
On 7/25/05, Mikael Ronström <mik...@mysql.com> wrote:
Pages are reusable after a table has been dropped and the other method of of retrieving pages after a major delete session is a "rolling upgrade" that will reorganise the data such that pages will be completely filled.
Mikael, Based on your comments then, does this mean that a table I have which grows at 7-8,000 records per hour, is inevitably doomed on MySQL Cluster technology? As I had planned to store the data for a couple of months, then cycle out old data to another database server, then delete the moved data. Dropping the table is out of the question due to the amount of updates and selects made the table. Does that leave me with initialling my nodes every node and then to reallocate everything in memory? As I had assumed that once you 'Delete' the data, that memory is once again made available to store table rows. Which does not seem to be the case.
Adam