Thanks for your quick response, Zhenya. I now can deploy the Ignite upgrade to prod with more confidences
Thanks. On Tue, May 17, 2022 at 6:50 PM Zhenya Stanilovsky <arzamas...@mail.ru> wrote: > Hello, Noah. Yep seems this behavior is mistaken, just filter out this log > somehow. > I fill the issue [1] > > [1] https://issues.apache.org/jira/browse/IGNITE-16989 > > > > > > > Hi all, > > I recently upgraded Ignite from 2.8.1 to 2.13 and started to obtain the > following annoying warning messages. > > 2022-05-17 01:03:29,633 [100] WRN [MutableCacheComputeServer] Failed to > ping node [nodeId=null]. Reached the timeout 10000ms. Cause: Connection > refused (Connection refused) > 2022-05-17 01:03:29,633 [100] WRN [MutableCacheComputeServer] Failed to > ping node [nodeId=null]. Reached the timeout 10000ms. Cause: Connection > refused (Connection refused) > 2022-05-17 01:03:29,634 [100] WRN [MutableCacheComputeServer] Failed to > ping node [nodeId=null]. Reached the timeout 10000ms. Cause: Connection > refused (Connection refused) > 2022-05-17 01:03:29,636 [100] WRN [MutableCacheComputeServer] Failed to > ping node [nodeId=null]. Reached the timeout 10000ms. Cause: Connection > refused (Connection refused) > 2022-05-17 01:03:29,637 [100] WRN [MutableCacheComputeServer] Failed to > ping node [nodeId=null]. Reached the timeout 10000ms. Cause: Connection > refused (Connection refused) > 2022-05-17 01:03:29,639 [100] WRN [MutableCacheComputeServer] Failed to > ping node [nodeId=null]. Reached the timeout 10000ms. Cause: Connection > refused (Connection refused) > > I tried to find any difference between 2.8.1 and 2.13 and found that the > newer version has added the following code which is to add those warning > messages. > if (spi.failureDetectionTimeoutEnabled() && timeoutHelper. > checkFailureTimeoutReached(e)) { > log.warning("Failed to ping node [nodeId=" + nodeId + "]. Reached the > timeout " + > spi.failureDetectionTimeout() + "ms. Cause: " + e.getMessage()); > > break; > } > > I really wonder which cases the `nodeId` can be null and how I can fix > this warning message. > Could anyone please help me avoid these messages and let me know which > cases the nodeId can null? > > Kind regards, > > > > > > > > >
