Dear All, By analyzing current corosync code, I found that if some messages can be generated from library during SYNC processing(such as reload/shutdown over cfgtool, because they are CS_LIB_FLOW_CONTROL_NOT_REQUIRED), or in other words, if they can be generated on new_message_queue_trans queue because instance->waiting_trans_ack was set to 1, then they may have chance to be originated after the last SYNC message. In this situation, they will be delivered after instance->waiting_trans_ack and totempg_waiting_transack set back to 0, then the assembly for the normal messages will be used to defrage those messages, not the expected assembly for the trans messages. This may finally result in lost normal messages due to fragment number is not equal to assembly last_frag_num. Please have a look if this really a problem or I have missed something? Thank you! -- Yours, Jason _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
