[
https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805890#comment-17805890
]
Evgeny Stanilovsky commented on IGNITE-21059:
---------------------------------------------
numerous :
{noformat}
Failed to connect to node (is node still alive?). Make sure that each
ComputeTask and cache Transaction has a timeout set in order to prevent parties
from waiting forever in case of network issues
[nodeId=08ee4a70-3342-4e3b-abd4-3999bbea57e4, addrs=[/10.244.11.201:47100,
/127.0.0.1:47100, 0:0:0:0:0:0:0:1%lo:47100]]
at
org.apache.ignite.spi.communication.tcp.internal.GridNioServerWrapper.createNioSession(GridNioServerWrapper.java:565)
~[ignite-core-2.14.0.jar:2.14.0]
{noformat}
network problems ?
{noformat}
Failed to connect to node (is node still alive?). Make sure that each
ComputeTask and cache Transaction has a timeout set in order to prevent parties
from waiting forever in case of network issues
[nodeId=08ee4a70-3342-4e3b-abd4-3999bbea57e4, addrs=[/10.244.11.201:47100,
/127.0.0.1:47100, 0:0:0:0:0:0:0:1%lo:47100]]
>> Selector info [id=0, keysCnt=2, bytesRcvd=86003560, bytesRcvd0=854,
>> bytesSent=280419496, bytesSent0=0]
Connection info [in=true, rmtAddr=/10.135.34.53:36796,
locAddr=/10.135.34.68:47100
{noformat}
> We have upgraded our ignite instance from 2.7.6 to 2.14. Found long running
> cache operations
> --------------------------------------------------------------------------------------------
>
> Key: IGNITE-21059
> URL: https://issues.apache.org/jira/browse/IGNITE-21059
> Project: Ignite
> Issue Type: Bug
> Components: binary, clients
> Affects Versions: 2.14
> Reporter: Vipul Thakur
> Priority: Critical
> Attachments: Ignite_server_logs.zip, cache-config-1.xml,
> client-service.zip, digiapi-eventprocessing-app-zone1-6685b8d7f7-ntw27.log,
> digiapi-eventprocessing-app-zone1-696c8c4946-62jbx-jstck.txt1,
> digiapi-eventprocessing-app-zone1-696c8c4946-62jbx-jstck.txt2,
> digiapi-eventprocessing-app-zone1-696c8c4946-62jbx-jstck.txt3,
> digiapi-eventprocessing-app-zone1-696c8c4946-7d57w-jstck.txt1,
> digiapi-eventprocessing-app-zone1-696c8c4946-7d57w-jstck.txt2,
> ignite-server-nohup-1.out, ignite-server-nohup.out, ignite_issue_1101.zip,
> image-2024-01-11-22-28-51-501.png, image.png, long_txn_.png, nohup_12.out
>
>
> We have recently upgraded from 2.7.6 to 2.14 due to the issue observed in
> production environment where cluster would go in hang state due to partition
> map exchange.
> Please find the below ticket which i created a while back for ignite 2.7.6
> https://issues.apache.org/jira/browse/IGNITE-13298
> So we migrated the apache ignite version to 2.14 and upgrade happened
> smoothly but on the third day we could see cluster traffic dip again.
> We have 5 nodes in a cluster where we provide 400 GB of RAM and more than 1
> TB SDD.
> PFB for the attached config.[I have added it as attachment for review]
> I have also added the server logs from the same time when issue happened.
> We have set txn timeout as well as socket timeout both at server and client
> end for our write operations but seems like sometimes cluster goes into hang
> state and all our get calls are stuck and slowly everything starts to freeze
> our jms listener threads and every thread reaches a choked up state in
> sometime.
> Due to which our read services which does not even use txn to retrieve data
> also starts to choke. Ultimately leading to end user traffic dip.
> We were hoping product upgrade will help but that has not been the case till
> now.
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
