Hello Michael,
Thursday, May 31, 2001, 11:19:03 PM, you wrote:
MW> Hi!
>>>>>> "Peter" == Peter Zaitsev <[EMAIL PROTECTED]> writes:
Peter>> Hello bugs,
Peter>> mysql 3.23.38
Peter>> Linux diamond 2.4.4.SuSE-12-4GB-SMP #8 SMP Sat May 19 21:24:05 MSD
Peter>> 2001 i686 unknown
Peter>> SUSE 7.1 (GLIBC 2.2.x)
Peter>> I've got to try to use BDB in my production-like enviroment and
Peter>> quickly got above error:
MW> <cut>
MW> select last from
MW> layers_st90.g00layers_stat_hits where counter=159806 and type=2
MW> and page_group=255 order
MW> by begin desc limit 1
MW> Peter, could you try to check if you can get the problem when just
MW> running the above query ?
Well. Sorry I fogot to write this. I do not get this then I run just this
query. There ara many different queries in my log file which finaly
leads to crash and about which applications gets an error (#1) before.
So It hapens like - application starts to get error #1 then trying to
execute the query and then finaly mysql crashes.
This error gets repeatable and stays before mysql restart or crash.
Here are some more queries which lead to crash wich exactly the same
backtrace, a bit different from the first one,
thd->query at 0x8588aa8 = SELECT
UNIX_TIMESTAMP(MAX(last)) AS uts
FROM
layers_st90.g00layers_stat_pagesactions
WHERE
counter = 138378
thd->thread_id = 42
thd->query at 0x856a160 = SELECT
UNIX_TIMESTAMP(MAX(last)) AS uts
FROM
layers_st90.g00layers_stat_hits
WHERE
counter = 138378
thd->thread_id = 13
Backtrace is:
0x8234988 pthread_sighandler + 168
0x80ba166 rnd_next__11ha_berkeleyPc + 74
0x80ad63e rr_sequential__FP14st_read_record + 122
0x80964d9 join_init_read_record__FP13st_join_table + 89
0x80915de sub_select__FP4JOINP13st_join_tableb + 86
0x80913a0 do_select__FP4JOINPt4List1Z4ItemP8st_tableP9Procedure + 404
0x808a8eb
mysql_select__FP3THDP13st_table_listRt4List1Z4ItemP4ItemRt4List1Z15Item_func_matchP8st_orderT5T3T5UiP13select_result
+ 5547
0x807308a mysql_execute_command__Fv + 758
0x8077074 mysql_parse__FP3THDPcUi + 216
0x8072314 do_command__FP3THD + 1436
0x8071707 handle_one_connection__FPv + 655
MW> <cut>
I Think this is a long outstanding bug - I got it, then I was trying
to play around with BDB first time (about 3 months ago). I wrote about
it but it was hard to repeat.
Peter>> 010531 18:16:22 /usr/local/mysql/libexec/mysqld: Got error -30989
Peter>> during CHECKPOINT
Peter>> 010531 18:16:22 bdb: log_archive: DB_ARCH_ABS: DB_RUNRECOVERY: Fatal
Peter>> error, run database recovery
Peter>> 010531 18:16:22 /usr/local/mysql/libexec/mysqld: Shutdown Complete
Peter>> So it seems like log files went dammaged.
Peter>> This is even more surprising as I had no machine crash or reboot...
MW> I agree; The above is something that should never happen.
MW> How many bdb tables do you have now?
About 1200. But only 120 of them are really used now (in test script).
MW> To be able to find and fix this, we would need a copy of the logs +
MW> the bdb tables to be able to make a bug report for the Sleepycat team.
So I packed it and uploaded into secret directory as
bdb_tables.tar.gz
log.0000003366.gz
MW> Have you had any luck with testing of InnoDB tables ?
Well. I'll play more now, after finding out there are some bugs with
BDB. I'm a bit afraid of INNODB tables as no
recovery tools exists, also it's more hard to make a backups.
Also It looks like I'll need to use many tablespaces to hold my
database as files grater then 2G is not supported yet.
Other think which is really bothering me - data migration which I
often have to do if some of my servers gets overload. So I just may
copy such databases with bdb or myisam but can't do so with INNODB.
My other tests show it's pretty fast, and I'll play more with it I
think.
--
Best regards,
Peter mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
