Odd slave lag, Master/Master Replication. (2 replies)

Hey all Im seeing some odd form of slave lag on a Master/Master replication setup.

First I have two nodes, with nodeA active and nodeB sitting idle other then replication.

The Active node (nodeA), is lagging behind the the slave node by a matter of days. (although show slave status says everythign is fine.)

example:

nodeB


NodeA:
"show master status\G"
*************************** 1. row ***************************
File: mysql-bin.009868
Position: 79570978
Binlog_Do_DB:
Binlog_Ignore_DB:

"ls -lt mysql-bin*"
-rw-rw---- 1 mysql mysql 98754192 Jan 13 11:33 mysql-bin.009868
... Many More ...
-rw-rw---- 1 mysql mysql 104913291 Jan 8 21:45 mysql-bin.008948


NodeB:
"show slave status\G"
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: NodeA
...
Master_Log_File: mysql-bin.008949
Read_Master_Log_Pos: 45280112
Relay_Log_File: db-relay-bin.002083
Relay_Log_Pos: 251
Relay_Master_Log_File: mysql-bin.008949
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
...
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 45280112
Relay_Log_Space: 446
...
Seconds_Behind_Master: 0
...


So two issues,
1. Why am I zero seconds behind master on NodeA if there are 5 days worth of logs to process... and why am I 5 days behind?

2. Why do I so many binary logs on a server that is not being written to, other then the replication thread?

Any help would be appreciated.

Thanks,