Am 15.12.2011 19:48, schrieb Paul DuBois:
>
> On Dec 15, 2011, at 12:02 PM, Reindl Harald wrote:
>
>> this is NOT a memory issue
>>
>> 'myisam_use_mmap' in mysqld is buggy since a long time
>> http://bugs.mysql.com/bug.php?id=48726
>
> This is fixed in 5.1.61, 5.5.20, 5.6.5:
>
> http://dev.my
On Dec 15, 2011, at 12:02 PM, Reindl Harald wrote:
> this is NOT a memory issue
>
> 'myisam_use_mmap' in mysqld is buggy since a long time
> http://bugs.mysql.com/bug.php?id=48726
This is fixed in 5.1.61, 5.5.20, 5.6.5:
http://dev.mysql.com/doc/refman/5.6/en/news-5-6-5.html
> we are speaking
this is NOT a memory issue
'myisam_use_mmap' in mysqld is buggy since a long time
http://bugs.mysql.com/bug.php?id=48726
we are speaking of a HP ProLiant DL 380G7 in a VMware-Cluster
with 36 GB ECC-RAM while there are machines using InnoDB
with 'large-pages' and some GB buffer_pool_size on the sa
When I had memory issues, with something relatively stable, mostly is due
faulty ram...
Can you use or less ram or change fisically the ram?
On Thu, Dec 15, 2011 at 2:23 AM, Reindl Harald wrote:
>
>
> Am 15.12.2011 08:47, schrieb Rob Wultsch:
> > To be brutally honest, if you want stability yo
Am 15.12.2011 08:47, schrieb Rob Wultsch:
> To be brutally honest, if you want stability you should
> not be using MyISAM
this is bullshit
without 'myisam_use_mmap' i never saw mysqld crashing
in the past 10 years, independent of the storage engine
> much less a not particularly commonly used
ec/mysqld(_Z24do_handle_one_connectionP3THD+0x117)[0x61fff7]
> /usr/libexec/mysqld(handle_one_connection+0x50)[0x6200a0]
> /lib64/libpthread.so.0(+0x6ccb)[0x7ffdaae8bccb]
> /lib64/libc.so.6(clone+0x6d)[0x7ffda91bdc2d]
>
> Trying to get some variables.
> Some pointers may be invalid an
ay be invalid and cause the dump to abort.
Query (0x7ffd20021720): is an invalid pointer
Connection ID (thread ID): 647
Status: NOT_KILLED
Original-Nachricht
Betreff: 'myisam_use_mmap' unstable like hell
Datum: Thu, 24 Nov 2011 09:20:28 +0100
Von: Reindl Harald
Organisation:
