[2.8.1]Received finish request for completed transaction (the message may be too late

classic Classic list List threaded Threaded
2 messages Options
38797715 38797715
Reply | Threaded
Open this post in threaded view
|

[2.8.1]Received finish request for completed transaction (the message may be too late

Hi community,

After the following parameters are configured, a large number of warning messages are output in the log. Why?

<property name="TxTimeoutOnPartitionMapExchange" value="20000"/>

Ilya Kazakov Ilya Kazakov
Reply | Threaded
Open this post in threaded view
|

Re: [2.8.1]Received finish request for completed transaction (the message may be too late

Hello, 38797715!

You have set some value for the parameter TxTimeoutOnPartitionMapExchange. This means that you allow Ignite to rollback "long" transactions when Ignite wants to start a partition map exchange process. A "long" transaction (its duration) you define in this parameter.

Well, when you see the warning "Received finish request for completed transaction (the message may be too late)", this means that Ignite wants to rollback some transaction and have sent the appropriate command. But at the moment when this command should be executed, the transaction is already finished by itself.


Regards, 
Ilya Kazakov

чт, 26 нояб. 2020 г. в 09:43, 38797715 <[hidden email]>:

Hi community,

After the following parameters are configured, a large number of warning messages are output in the log. Why?

<property name="TxTimeoutOnPartitionMapExchange" value="20000"/>