Re: GridTimeoutProcessor - Timeout has occurred - Too frequent messages

2019-03-14 Thread Павлухин Иван
Hi, Yes, perhaps there is no reach documentation for mentioned classes. But on the other hand they are internal classes which could be changed at any time. I will try to outline roles for 2 classes. 1. CancellableTask is used internally as a general way to cancel some action sheduled in the

Re: GridTimeoutProcessor - Timeout has occurred - Too frequent messages

2019-03-11 Thread userx
Hi Ivan, Thanks for the reply. I totally buy your point that these messages are not bad. What I wanted to understand basically was the role of the following GridTimeOut objects 1) CancelableTask 2) GridCommunicationMessageSet 3) CacheContinuousQueryManager$BackupCleaner There is no

Re: GridTimeoutProcessor - Timeout has occurred - Too frequent messages

2019-03-11 Thread Павлухин Иван
Hi, There is nothing bad with message you see. GridTimeoutProcessor is used internally by Ignite for scheduling a task execution after a delay. Debug message "Timeout has occurred" is logged every time scheduling delay has ended. It is a debug message and a purpose of it is checking that

Re: GridTimeoutProcessor - Timeout has occurred - Too frequent messages

2019-03-08 Thread userx
Hi, Any thoughts on the same. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/