Re: Shutting down one server, creates a new logfile every few seconds

Hi!

>>>>> "Melvyn" == Melvyn Sopacua writes:

>Description:
> When one of the servers in a replication scheme, where master =
> slave of master,
> goes down, the servers replicate eachothers 'set logfile' command.
> This results in a new logfile being created every few seconds and
> tying up server resources.
>>
Sasha> Thanks for reporting the bug. This is a known problem, and is fixed in 4.0.2.

Melvyn> Nope it is not.



Melvyn> Can you please look into it again?

I have done a bug overhaul of the replication code for 4.0.3 and it's
now possible that this is fixed. If not, I will fix this in 4.0.4

If this doesn't work in 4.0.3, could you please do a test case for
this so that I can easily reproduce this and then fix it?

Regards,
Monty



------------------------------------------------------------ ---------
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 bugs-thread12374@lists.mysql.com
To unsubscribe, e-mail

Re: Shutting down one server, creates a new logfile every few seconds

Hi,

On Mon, 19 Aug 2002, Michael Widenius wrote:

MW>>> >Description:
MW>>> > When one of the servers in a replication scheme, where master =
MW>>> > slave of master,
MW>>> > goes down, the servers replicate eachothers 'set logfile' command.
MW>>> > This results in a new logfile being created every few seconds and
MW>>> > tying up server resources.
MW>>> >>

[...]

MW>>> Melvyn> Can you please look into it again?
MW>>>
MW>>> I have done a bug overhaul of the replication code for 4.0.3 and it's
MW>>> now possible that this is fixed. If not, I will fix this in 4.0.4
MW>>>
MW>>> If this doesn't work in 4.0.3, could you please do a test case for
MW>>> this so that I can easily reproduce this and then fix it?

I'll take a look at the test suite, how master/slave tests are setup, and
see what I can come up with.

It basically boils down to:
set up the master/slave=slave/master twin A and B
insert stuff on A, so replication is started
shut A or B down and bring it back up



------------------------------------------------------------ ---------
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 bugs-thread12375@lists.mysql.com
To unsubscribe, e-mail

4.0.2-alpha-nt-log table corruption bug

The following table corruption can be repeated. I have reproduced this
problem on
more several PC's. In all cases, it was tested on Win32 (WinNT, 2000 and
XP).
The following table has been in production for over a year. Upgrading from
4.0.1-alpha-nt-log to 4.0.2-alpha-nt-log causes corruption.

FYI, same corruption occures with 4.0.2-alpha-nt-max-log

I have supplied the table structure and sample sql to reporduce this bug.

The steps to create bug...
1: Create table (table structure below)
2: Insert record
3: run CHECK TABLE sfmain


mysql> check table sfmain;
+------------------+-------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+------------------+-------+----------+----------+
| socaldata.sfmain | check | status | OK |
+------------------+-------+----------+----------+
1 row in set (1.02 sec)

mysql> insert into sfMain ( COMPANY_CD, PRODUCT_CD, TYPE, SUBMIT_BY, EXT,
REASON,
TIME_SUBMIT, HOT_DATE, ADP_WEEK, ADP_YEAR_WEEK, SYSTEM, HOT, CONAME,
CONTACT_NA,
PHONE, ADDRESS1_I, ADDRESS2_I, CITY_I, STATE_I, ZIP_I, TRIP_D, AR_NUMBER,
ERROR_CODE,
CHARGE,
-> RESP_CSR_CODE, CSR_CODE, TEAM, DEL_SPECIAL, SIGNOFF_1, SIGNOFF_2,
SIGNOFF_3,
SIGNOFF_4, SIGNOFF_5, SIGNOFF_6, SIGNOFF_7, SIGNOFF_8, FORM_NO, BILLING)
values(
'XGC', '10', 'RR', 'RICK ', '1212', 'TEST', '1426', '20020819', '34',
'200234',
'1', 'N',
-> 'PRODUCTION TEST', 'TEST', '7149942000', '5355 ORANGETHORPE AVE', '',
'LA PALMA',
'CA', '90623', 'X00', '1234567', '99', 'No', 'WW', 'ZZ', 'A', 'NORMAL',
'Y', 'Y', 'Y', 'N', 'N', 'N', 'N', 'N', '001', 'N')
-> ;
Query OK, 1 row affected (0.01 sec)

mysql> SELECT LAST_INSERT_ID();
+------------------+
| last_insert_id() |
+------------------+
| 48627 |
+------------------+
1 row in set (0.00 sec)

mysql> check table sfmain;
+------------------+-------+----------+--------------------- ----------------
--------------------+
| Table | Op | Msg_type | Msg_text |
+------------------+-------+----------+--------------------- ----------------
--------------------+
| socaldata.sfmain | check | warning | Size of datafile is: 6810436
Should be: 6810252 |
| socaldata.sfmain | check | error | Record-count is not ok; is 34631
Should be: 34630 |
| socaldata.sfmain | check | warning | Found 34631 parts
Shouldbe: 34630 parts |
| socaldata.sfmain | check | error | Corrupt |
+------------------+-------+----------+--------------------- ----------------
--------------------+
4 rows in set (0.63 sec)

mysql>

Table Structure...

create table sfmain (
RERUN_NO int(11) not null auto_increment,
COMPANY_CD varchar(6) ,
PRODUCT_CD char(2) ,
RR_SIGNOFF char(2) ,
TYPE varchar(4) ,
SUBMIT_BY varchar(25) ,
EXT varchar(15) ,
REASON varchar(254) ,
TIME_SUBMIT smallint(6) ,
TIME_TRAFFIC smallint(6) ,
TIME_TRAFF smallint(6) ,
REVISED smallint(6) ,
OUTPUT_TO varchar(25) ,
REG_HOT char(3) ,
WRAP_CMPL smallint(6) ,
COMPLETED smallint(6) ,
HOT_DATE date ,
COMMENTS varchar(254) ,
ADP_WEEK tinyint(4) ,
ADP_YEAR_WEEK mediumint(6) ,
SYSTEM char(1) ,
TRAFF_REC smallint(6) ,
TRAFF_ETA smallint(6) ,
HOT char(1) default 'N' ,
CONAME varchar(30) ,
CONTACT_NA varchar(25) ,
PHONE varchar(14) ,
ADDRESS1_I varchar(30) ,
ADDRESS2_I varchar(30) ,
CITY_I varchar(30) ,
STATE_I char(2) ,
ZIP_I varchar(10) ,
TRIP_D char(3) ,
AR_NUMBER varchar(12) ,
ERROR_CODE char(3) ,
CHARGE char(1) default 'N' ,
RESP_CSR_CODE char(2) ,
CSR_CODE char(2) ,
TEAM char(1) ,
DEL_SPECIAL varchar(254) ,
SIGNOFF_1 char(1) default 'N' ,
SIGNOFF_2 char(1) default 'N' ,
SIGNOFF_3 char(1) default 'N' ,
SIGNOFF_4 char(1) default 'N' ,
SIGNOFF_5 char(1) default 'N' ,
SIGNOFF_6 char(1) default 'N' ,
SIGNOFF_7 char(1) default 'N' ,
SIGNOFF_8 char(1) default 'N' ,
PRINT_DATE date ,
PRINT_TIME time ,
PRINT_CK char(1) default 'N' ,
FORM_NO char(3) ,
REC_TIME timestamp(14) ,
CHANGED datetime ,
IN_USE_USER varchar(13) ,
DELIVERY_DATE date ,
CANCELLED char(1) default 'N' ,
METHOD_CD char(2) ,
BILLING char(1) default 'N' ,
PRIMARY KEY (RERUN_NO),
KEY complete (COMPLETED, COMPANY_CD),
KEY timeCoCodeSort (TIME_TRAFF, COMPANY_CD)
)

MySQL Server environment...

back_log 50
basedir d:\mysql\
binlog_cache_size 32768
character_set latin1
character_sets latin1 big5 czech euc_kr gb2312 gbk latin1_de
sjis
concurrent_insert OFF
connect_timeout 5
datadir d:\mysql\data\
delay_key_write OFF
delayed_insert_limit 100
delayed_insert_timeout 300
delayed_queue_size 1000
flush OFF
flush_time 1800
ft_min_word_len 4
ft_max_word_len 254
ft_max_word_len_for_sort 20
ft_boolean_syntax + -><()~*:""&|
have_bdb NO
have_innodb NO
have_isam YES
have_raid NO
have_symlink YES
have_openssl NO
have_query_cache NO
init_file
interactive_timeout 28800
join_buffer_size 131072
key_buffer_size 402649088
language d:\mysql\share\english\
large_files_support ON
log ON
log_update OFF
log_bin OFF
log_slave_updates OFF
log_slow_queries OFF
long_query_time 10
low_priority_updates OFF
lower_case_table_names 0
max_allowed_packet 1047552
max_binlog_cache_size 4294967295
max_binlog_size 1073741824
max_connections 300
max_connect_errors 10
max_delayed_threads 20
max_heap_table_size 16777216
max_join_size 4294967295

max_sort_length 1024
max_user_connections 0
max_tmp_tables 32
max_write_lock_count 4294967295
myisam_bulk_insert_tree_size 8388608
myisam_max_extra_sort_file_size256
myisam_max_sort_file_size 2047
myisam_recover_options OFF
myisam_sort_buffer_size 67108864
named_pipe OFF
net_buffer_length 16384
net_read_timeout 30
net_retry_count 10
net_write_timeout 60
open_files_limit 0
pid_file d:\mysql\data\REGIT-DEV1.pid
port 3306
protocol_version 10
record_buffer 4190208
record_rnd_buffer 4190208
rpl_recovery_rank 0
query_buffer_size 0
safe_show_database OFF
server_id 1
slave_net_timeout 3600
skip_locking ON
skip_networking OFF
skip_show_database OFF
slow_launch_time 2
socket MySQL
sort_buffer 8388600
sql_mode 0
table_cache 512
table_type MYISAM
thread_cache_size 8
thread_stack 65536
transaction_isolation READ-COMMITTED
timezone Pacific Standard Time
tmp_table_size 33554432
tmpdir C:\WINDOWS\TEMP\
version 4.0.2-alpha-nt-log
wait_timeout 28800



------------------------------------------------------------ ---------
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 bugs-thread12377@lists.mysql.com
To unsubscribe, e-mail

Re: 4.0.2-alpha-nt-log table corruption bug

Fredrick Bartlett writes:
> The following table corruption can be repeated. I have reproduced this
> problem on
> more several PC's. In all cases, it was tested on Win32 (WinNT, 2000 and
> XP).
> The following table has been in production for over a year. Upgrading from
> 4.0.1-alpha-nt-log to 4.0.2-alpha-nt-log causes corruption.
>
> FYI, same corruption occures with 4.0.2-alpha-nt-max-log
>
> I have supplied the table structure and sample sql to reporduce this bug.
>
> The steps to create bug...
> 1: Create table (table structure below)
> 2: Insert record
> 3: run CHECK TABLE sfmain
>
>

Hi!

I have tested your case on Linux with 4.0.3 and similar setup, and no
problems were encountered.

I will ask our Windows expert to test your case.

--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com


------------------------------------------------------------ ---------
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 bugs-thread12385@lists.mysql.com
To unsubscribe, e-mail

Re: 4.0.2-alpha-nt-log table corruption bug

The problem occurs in 4.0.2-nt. Did you test in 4.0.2-nt?
How can I get a fixed 4.0.3-nt binary exe?

----- Original Message -----
From: "Sinisa Milivojevic"
To:
Cc:
Sent: Tuesday, August 20, 2002 10:43 AM
Subject: Re: 4.0.2-alpha-nt-log table corruption bug


>
> Hi!
>
> Your test case was also tested by our Windows expert (with 4.0.3) and
> all tests passed without any corruption to the table.
>
> --
> Regards,
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
> /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
> <___/ www.mysql.com
>
>



------------------------------------------------------------ ---------
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 bugs-thread12386@lists.mysql.com
To unsubscribe, e-mail

Re: 4.0.2-alpha-nt-log table corruption bug

----- Original Message -----
From: "miguel solorzano"
To: "Fredrick Bartlett" ;
Cc:
Sent: Tuesday, August 20, 2002 4:14 PM
Subject: Re: 4.0.2-alpha-nt-log table corruption bug


At 15:34 20/08/02 -0700, Fredrick Bartlett wrote:
Hi,

>The problem occurs in 4.0.2-nt. Did you test in 4.0.2-nt?
>How can I get a fixed 4.0.3-nt binary exe?

I did the test and I wasn't able to repeat according your
instructions:

mysql> CHECK TABLE sfmain;
+-------------+-------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+-------------+-------+----------+----------+
| test.sfmain | check | status | OK |
+-------------+-------+----------+----------+
1 row in set (0.00 sec)

Are you using replication ?

No replication. Did you test with the binary 4.02-nt from the public
download domain?
Here is my start up options in my.cnf. Does it look ok for 512 ram?
Try adding: "lower_case_table_names = 0"
Then insert a few records and the table will corrupt.

[mysqld]
basedir=d:/mysql
port=3306
log=/mysql/logfiles/activity.log
skip-locking
set-variable = max_connections=300
set-variable = key_buffer=384M
set-variable = max_allowed_packet=1M
set-variable = table_cache=512
set-variable = sort_buffer=8M
set-variable = record_buffer=4M
set-variable = thread_cache=8
# Try number of CPU's*2 for thread_concurrency
set-variable = thread_concurrency=2
set-variable = myisam_sort_buffer_size=64M
server-id = 1
lower_case_table_names = 0

Regards,

>----- Original Message -----
>From: "Sinisa Milivojevic"
>To:
>Cc:
>Sent: Tuesday, August 20, 2002 10:43 AM
>Subject: Re: 4.0.2-alpha-nt-log table corruption bug
>
>
> >
> > Hi!
> >
> > Your test case was also tested by our Windows expert (with 4.0.3) and
> > all tests passed without any corruption to the table.
> >
> > --
> > Regards,
> > __ ___ ___ ____ __
> > / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
> > / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
> > /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
> > <___/ www.mysql.com
> >
> >
>

--
For technical support contracts, visit https//order.mysql.com
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Miguel Angel Solórzano
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ São Paulo - Brazil
<___/ www.mysql.com




------------------------------------------------------------ ---------
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 bugs-thread12387@lists.mysql.com
To unsubscribe, e-mail

Re: 4.0.2-alpha-nt-log table corruption bug

Hi!

miguel solorzano writes:
> At 20:00 20/08/02 -0700, Fredrick Bartlett wrote:
> Hi,
>
> >Cc:
> >Sent: Tuesday, August 20, 2002 4:14 PM
> >Subject: Re: 4.0.2-alpha-nt-log table corruption bug
> >
> >
> >At 15:34 20/08/02 -0700, Fredrick Bartlett wrote:
> >Hi,
> >
> > >The problem occurs in 4.0.2-nt. Did you test in 4.0.2-nt?
> > >How can I get a fixed 4.0.3-nt binary exe?
> >
> >I did the test and I wasn't able to repeat according your
> >instructions:
> >
> >mysql> CHECK TABLE sfmain;
> >+-------------+-------+----------+----------+
> >| Table | Op | Msg_type | Msg_text |
> >+-------------+-------+----------+----------+
> >| test.sfmain | check | status | OK |
> >+-------------+-------+----------+----------+
> >1 row in set (0.00 sec)
> >
> >Are you using replication ?
> >
> >No replication. Did you test with the binary 4.02-nt from the public
> >download domain?
>
> Yes.
>
> >Here is my start up options in my.cnf. Does it look ok for 512 ram?
> >Try adding: "lower_case_table_names = 0"
>
> Now I was be able to repeat the same issue and that the culprit is:
>
> lower_case_table_names = 0
>
> I am CC for Jani, since I saw some fixes made by him relative
> to lower_case_table_names and maybe these ones will fix the
> problem in the next release 4.0.3.

Yes, there were a couple of fixes specially regarding
--lower_case_table_name option/variable between versions 4.0.2
and 4.0.3.

4.0.3 should come out quite soon, so I suggest you try that when
ready, it will probably fix the bug.

> Regards,
>
> >Then insert a few records and the table will corrupt.

Regards,

- Jani

For technical support contracts, visit https://order.mysql.com/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Jani Tolonen
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Helsinki, Finland
<___/ www.mysql.com

------------------------------------------------------------ ---------
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 bugs-thread12388@lists.mysql.com
To unsubscribe, e-mail

4.0.3-alpha-nt-log table corruption bug

I reported the following and is still occuring in 4.0.3-beta-nt.
Miguel Angel Solórzano was able to reproduce it in 4.0.2

>Now I was be able to repeat the same issue and that the culprit is:
>
>lower_case_table_names = 0
>
>I am CC for Jani, since I saw some fixes made by him relative
>to lower_case_table_names and maybe these ones will fix the
>problem in the next release 4.0.3.
>
>Regards,
>--
>For technical support contracts, visit https//order.mysql.com
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Miguel Angel Solórzano
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
>/_/ /_/\_, /___/\___\_\___/ São Paulo - Brazil
> <___/ www.mysql.com

The following table corruption can be repeated. I have reproduced this
problem on
more several PC's. In all cases, it was tested on Win32 (WinNT, 2000 and
XP).
The following table has been in production for over a year. Upgrading from
4.0.1-alpha-nt-log to 4.0.2-alpha-nt-log causes corruption.(Now 4.03 as
well)

FYI, same corruption occures with 4.0.2-alpha-nt-max-log

I have supplied the table structure and sample sql to reporduce this bug.

The steps to create bug...
1: Create table (table structure below)
2: Insert record
3: run CHECK TABLE sfmain


mysql> check table sfmain;
+------------------+-------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+------------------+-------+----------+----------+
| socaldata.sfmain | check | status | OK |
+------------------+-------+----------+----------+
1 row in set (1.02 sec)

mysql> insert into sfMain ( COMPANY_CD, PRODUCT_CD, TYPE, SUBMIT_BY, EXT,
REASON,
TIME_SUBMIT, HOT_DATE, ADP_WEEK, ADP_YEAR_WEEK, SYSTEM, HOT, CONAME,
CONTACT_NA,
PHONE, ADDRESS1_I, ADDRESS2_I, CITY_I, STATE_I, ZIP_I, TRIP_D, AR_NUMBER,
ERROR_CODE,
CHARGE,
-> RESP_CSR_CODE, CSR_CODE, TEAM, DEL_SPECIAL, SIGNOFF_1, SIGNOFF_2,
SIGNOFF_3,
SIGNOFF_4, SIGNOFF_5, SIGNOFF_6, SIGNOFF_7, SIGNOFF_8, FORM_NO, BILLING)
values(
'XGC', '10', 'RR', 'RICK ', '1212', 'TEST', '1426', '20020819', '34',
'200234',
'1', 'N',
-> 'PRODUCTION TEST', 'TEST', '7149942000', '5355 ORANGETHORPE AVE', '',
'LA PALMA',
'CA', '90623', 'X00', '1234567', '99', 'No', 'WW', 'ZZ', 'A', 'NORMAL',
'Y', 'Y', 'Y', 'N', 'N', 'N', 'N', 'N', '001', 'N')
-> ;
Query OK, 1 row affected (0.01 sec)

mysql> SELECT LAST_INSERT_ID();
+------------------+
| last_insert_id() |
+------------------+
| 48627 |
+------------------+
1 row in set (0.00 sec)

mysql> check table sfmain;
+------------------+-------+----------+--------------------- ----------------
--------------------+
| Table | Op | Msg_type | Msg_text |
+------------------+-------+----------+--------------------- ----------------
--------------------+
| socaldata.sfmain | check | warning | Size of datafile is: 6810436
Should be: 6810252 |
| socaldata.sfmain | check | error | Record-count is not ok; is 34631
Should be: 34630 |
| socaldata.sfmain | check | warning | Found 34631 parts
Shouldbe: 34630 parts |
| socaldata.sfmain | check | error | Corrupt |
+------------------+-------+----------+--------------------- ----------------
--------------------+
4 rows in set (0.63 sec)

mysql>

Table Structure...

create table sfmain (
RERUN_NO int(11) not null auto_increment,
COMPANY_CD varchar(6) ,
PRODUCT_CD char(2) ,
RR_SIGNOFF char(2) ,
TYPE varchar(4) ,
SUBMIT_BY varchar(25) ,
EXT varchar(15) ,
REASON varchar(254) ,
TIME_SUBMIT smallint(6) ,
TIME_TRAFFIC smallint(6) ,
TIME_TRAFF smallint(6) ,
REVISED smallint(6) ,
OUTPUT_TO varchar(25) ,
REG_HOT char(3) ,
WRAP_CMPL smallint(6) ,
COMPLETED smallint(6) ,
HOT_DATE date ,
COMMENTS varchar(254) ,
ADP_WEEK tinyint(4) ,
ADP_YEAR_WEEK mediumint(6) ,
SYSTEM char(1) ,
TRAFF_REC smallint(6) ,
TRAFF_ETA smallint(6) ,
HOT char(1) default 'N' ,
CONAME varchar(30) ,
CONTACT_NA varchar(25) ,
PHONE varchar(14) ,
ADDRESS1_I varchar(30) ,
ADDRESS2_I varchar(30) ,
CITY_I varchar(30) ,
STATE_I char(2) ,
ZIP_I varchar(10) ,
TRIP_D char(3) ,
AR_NUMBER varchar(12) ,
ERROR_CODE char(3) ,
CHARGE char(1) default 'N' ,
RESP_CSR_CODE char(2) ,
CSR_CODE char(2) ,
TEAM char(1) ,
DEL_SPECIAL varchar(254) ,
SIGNOFF_1 char(1) default 'N' ,
SIGNOFF_2 char(1) default 'N' ,
SIGNOFF_3 char(1) default 'N' ,
SIGNOFF_4 char(1) default 'N' ,
SIGNOFF_5 char(1) default 'N' ,
SIGNOFF_6 char(1) default 'N' ,
SIGNOFF_7 char(1) default 'N' ,
SIGNOFF_8 char(1) default 'N' ,
PRINT_DATE date ,
PRINT_TIME time ,
PRINT_CK char(1) default 'N' ,
FORM_NO char(3) ,
REC_TIME timestamp(14) ,
CHANGED datetime ,
IN_USE_USER varchar(13) ,
DELIVERY_DATE date ,
CANCELLED char(1) default 'N' ,
METHOD_CD char(2) ,
BILLING char(1) default 'N' ,
PRIMARY KEY (RERUN_NO),
KEY complete (COMPLETED, COMPANY_CD),
KEY timeCoCodeSort (TIME_TRAFF, COMPANY_CD)
)

MySQL Server environment...

back_log 50
basedir d:\mysql\
binlog_cache_size 32768
character_set latin1
character_sets latin1 big5 czech euc_kr gb2312 gbk latin1_de
sjis
concurrent_insert OFF
connect_timeout 5
datadir d:\mysql\data\
delay_key_write OFF
delayed_insert_limit 100
delayed_insert_timeout 300
delayed_queue_size 1000
flush OFF
flush_time 1800
ft_min_word_len 4
ft_max_word_len 254
ft_max_word_len_for_sort 20
ft_boolean_syntax + -><()~*:""&|
have_bdb NO
have_innodb NO
have_isam YES
have_raid NO
have_symlink YES
have_openssl NO
have_query_cache NO
init_file
interactive_timeout 28800
join_buffer_size 131072
key_buffer_size 402649088
language d:\mysql\share\english\
large_files_support ON
log ON
log_update OFF
log_bin OFF
log_slave_updates OFF
log_slow_queries OFF
long_query_time 10
low_priority_updates OFF
lower_case_table_names 0
max_allowed_packet 1047552
max_binlog_cache_size 4294967295
max_binlog_size 1073741824
max_connections 300
max_connect_errors 10
max_delayed_threads 20
max_heap_table_size 16777216
max_join_size 4294967295

max_sort_length 1024
max_user_connections 0
max_tmp_tables 32
max_write_lock_count 4294967295
myisam_bulk_insert_tree_size 8388608
myisam_max_extra_sort_file_size256
myisam_max_sort_file_size 2047
myisam_recover_options OFF
myisam_sort_buffer_size 67108864
named_pipe OFF
net_buffer_length 16384
net_read_timeout 30
net_retry_count 10
net_write_timeout 60
open_files_limit 0
pid_file d:\mysql\data\REGIT-DEV1.pid
port 3306
protocol_version 10
record_buffer 4190208
record_rnd_buffer 4190208
rpl_recovery_rank 0
query_buffer_size 0
safe_show_database OFF
server_id 1
slave_net_timeout 3600
skip_locking ON
skip_networking OFF
skip_show_database OFF
slow_launch_time 2
socket MySQL
sort_buffer 8388600
sql_mode 0
table_cache 512
table_type MYISAM
thread_cache_size 8
thread_stack 65536
transaction_isolation READ-COMMITTED
timezone Pacific Standard Time
tmp_table_size 33554432
tmpdir C:\WINDOWS\TEMP\
version 4.0.2-alpha-nt-log
wait_timeout 28800




------------------------------------------------------------ ---------
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 bugs-thread12472@lists.mysql.com
To unsubscribe, e-mail

4.0.3-alpha-nt-log table corruption bug

Hi!

>>>>> "Fredrick" == Fredrick Bartlett w=
rites:

Fredrick> I reported the following and is still occuring in 4.0.3-beta-=
nt.
Fredrick> Miguel Angel Sol=F3rzano was able to reproduce it in 4.0.2



Fredrick> The following table corruption can be repeated. I have reprod=
uced this
Fredrick> problem on
Fredrick> more several PC's. In all cases, it was tested on Win32 (WinN=
T, 2000 and
Fredrick> XP).



Fredrick> The steps to create bug...
Fredrick> 1: Create table (table structure below)
Fredrick> 2: Insert record
Fredrick> 3: run CHECK TABLE sfmain


Thanks for the test case.

We fixed a couple of days a bug in CHECK table that could have caused
this behavior. I will ensure that your test case works before we
start building 4.0.4 binaries.

Regards,
Monty

------------------------------------------------------------ ---------
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 bugs-thread12480@lists.mysql.com
To unsubscribe, e-mail

Re: Shutting down one server, creates a new logfile every few seconds

On Monday 19 August 2002 21:34, Michael Widenius wrote:

> >>>>> "Melvyn" == Melvyn Sopacua writes:
> >
> >Description:
> > When one of the servers in a replication scheme, where master =3D
> > slave of master,
> > goes down, the servers replicate eachothers 'set logfile' command.
> > This results in a new logfile being created every few seconds and
> > tying up server resources.

[..]

> I have done a bug overhaul of the replication code for 4.0.3 and it's
> now possible that this is fixed. If not, I will fix this in 4.0.4
>
> If this doesn't work in 4.0.3, could you please do a test case for
> this so that I can easily reproduce this and then fix it?

It is not fixed in 4.0.3.

Monty - if you need access to these systems, just let me know where to se=
nd=20
the details. It will have to be SSH, preferably SSH2 protocol.

I tried doing this with a testcase, but couldn't reproduce it, I think it=
=20
needs actual network network traffic.

Here's our situation:

Machine 'hanneke', ip-addresses:
192.168.100.121
192.168.101.121
master_host 192.168.101.120
master_user: replicate
master_port: 3406

Config:
log-bin =3D /data/sql/logs/rep_log

Machine 'femke', ip-addresses:
192.168.100.120
192.168.101.120
master_host: 192.168.101.121
master_user: replicate
master_port: 3406

Config:
log-bin =3D /data/mdev/sql/logs/rep_log

They both have different passwords. Both get queries from the webservers =
at=20
the 192.168.100 interface and replicate at 192.168.101 interface, so the=20
traffice doesn't bite.

Grants:
GRANT SELECT, FILE, SHOW DATABASES, CREATE TEMPORARY TABLES, LOCK TABLES,=
=20
REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'replicate'@'192.168.101.=
121'=20
IDENTIFIED BY 'scrambled';

And vice versa.

How-To-Repeat:
Setup the above configuration, preferably at an AIX 4.3.3 system as I hav=
en't=20
tested another OS.

Then start them both up without skip-slave-start and voila.

How-To-Resolve:
Issue SLAVE STOP on one of them and hope, that the master is already skip=
ped=20
ahead. Then issue:
CHANGE MASTER TO MASTER_LOG_FILE=3D'rep_log.5086', MASTER_LOG_POS=3D4;
SLAVE START;

Remarks:
The 'skip-locking' setting has no effect on this issue.

--=20
Best regards,

IDG.nl
Melvyn Sopacua
WebMaster

------------------------------------------------------------ ---------
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 bugs-thread12509@lists.mysql.com
To unsubscribe, e-mail

4.0.2-alpha-nt-log table corruption bug

Hi!

>>>>> "Fredrick" == Fredrick Bartlett writes:

Fredrick> The following table corruption can be repeated. I have reproduced this
Fredrick> problem on
Fredrick> more several PC's. In all cases, it was tested on Win32 (WinNT, 2000 and
Fredrick> XP).



Fredrick> The steps to create bug...
Fredrick> 1: Create table (table structure below)
Fredrick> 2: Insert record
Fredrick> 3: run CHECK TABLE sfmain

Just a note; In 4.0.4 we have fixed the bug that probably caused this
problem.

We are now doing test builds of 4.0.4 and it should be available
shortly.

Regards,
Monty

--
For technical support contracts, goto https://order.mysql.com/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Michael Widenius
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, CTO
/_/ /_/\_, /___/\___\_\___/ Helsinki, Finland
<___/ www.mysql.com

------------------------------------------------------------ ---------
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 bugs-thread12609@lists.mysql.com
To unsubscribe, e-mail