I am using the version 3.4.7 and when I scheduled a reload for a node I can see multiple channels synchronizing and throwing errors at the same time and I do not think this is normal.
FK errors on a reload are often a result of different FK constraints on the Server and the client. Symmetric will order the table reloads by the FK constraints at the originating node.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, I know that. My comment is not about the errors. I am pointing about the fact that multiples channel are synchronizing at the same time: reload and official.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using the version 3.4.7 and when I scheduled a reload for a node I can see multiple channels synchronizing and throwing errors at the same time and I do not think this is normal.
This is a view of the sym_outgoing_batch table:
batch_id | node_id | channel_id | status | load_flag | error_flag | common_flag | ignore_count | byte_count | extract_count | sent_count | load_count | data_event_count | reload_event_count | insert_event_count | update_event_count | delete_event_count | other_event_count | router_millis | network_millis | filter_millis | load_millis | extract_millis | sql_state | sql_code | sql_message | failed_data_id | failed_line_number | last_update_hostname | last_update_time | create_time | load_id | create_by
----------+-------------------------+------------+--------+-----------+------------+-------------+--------------+------------+---------------+------------+------------+------------------+--------------------+--------------------+--------------------+--------------------+-------------------+---------------+----------------+---------------+-------------+----------------+-----------+----------+---------------------------------------------------------------------------------------------------------------------------------------+----------------+--------------------+----------------------+-------------------------+----------------------------+---------+-----------
6883647 | Z_1_c_406_c_MeMeMi2klx6 | official | LD | 0 | 1 | 0 | 0 | 2535 | 6 | 1570 | 1570 | 2 | 0 | 0 | 2 | 0 | 0 | 1613 | 0 | 0 | 2 | 452 | 23503 | 0 | ERROR: insert or update on table "r_modality_student" violates foreign key constraint "r_modality_student_modality_id_tb_modality_id"+| 106361158 | 0 | ubuntu | 2013-06-21 15:15:24.987 | 2013-06-19 21:50:21.911493 | -1 |
| | | | | | | | | | | | | | | | | | | | | | | | | Detail: Key (modality_id)=(Z_1_c_406_c_MeMeMi2klx6_c_98_c_1551) is not present in table "tb_modality". | | | | | | |
6879323 | Z_1_c_406_c_MeMeMi2klx6 | reload | ER | 1 | 1 | 0 | 0 | 1258776 | 6 | 3116 | 1551 | 58781 | 1 | 58781 | 0 | 0 | 0 | 0 | 0 | 378 | 5602 | 662 | 23503 | 0 | ERROR: insert or update on table "r_lifecycle" violates foreign key constraint "r_lifecycle_lifecycle_id_tb_lifecycle_id" +| 0 | 0 | ubuntu | 2013-06-21 15:15:13.005 | 2013-06-19 20:58:57.333691 | 2 |
| | | | | | | | | | | | | | | | | | | | | | | | | Detail: Key (lifecycle_id)=(Z_9_c_871_c_MeMeSa5vpow_c_21104_c_10) is not present in table "tb_lifecycle". | | | | | | |
FK errors on a reload are often a result of different FK constraints on the Server and the client. Symmetric will order the table reloads by the FK constraints at the originating node.
Yes, I know that. My comment is not about the errors. I am pointing about the fact that multiples channel are synchronizing at the same time: reload and official.