1) This column is not used anymore, so the value of the updated column does not matter. The default is pending, we changed it to ok at some time because people that read the data in the database were asking why its still pending.
I think sys_datalog is supposed to delete old records after one moth?
In general, yes. But ist a bit more complicated. I copied the command which explains the requirements for records to be deleted from the sourcecode file:
* The sys_datalog is more difficult.
* 1) We have to keet ALL entries with
* server_id=0, because they depend on ALL servers (even if they are not
* actually in the system (and will be insered in 3 days or so).
* 2) We have to keey ALL entries which are not actually precessed by the
* server never mind how old they are!
* 3) We have to keep the entry with the highest autoinc-id, because mysql calculates the
* autoinc-id as "new value = max(row) +1" and does not store this in a separate table.
* This means, if we delete to entry with the highest autoinc-value then this value is
* reused as autoinc and so there are more than one entries with the same value (over
* for example 4 Weeks). This is confusing for our system.
* ATTENTION 2) and 3) is in some case NOT the same! so we have to check both!
sys_datalog table on all slaves is empty.
is it supposed work this way ?
Yes, as all slaves read the datalog from the master and use it to insert records in their database tables.