[
https://issues.apache.org/jira/browse/IGNITE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806049#comment-17806049
]
Evgeny Stanilovsky commented on IGNITE-21059:
---------------------------------------------
all logs spammed with
{noformat}
[2024-01-11T21:47:48,434][ERROR][client-connector-#3179%EVENT_PROCESSING%][TcpCommunicationSpi]
Failed to send message to remote node [node=TcpDiscoveryNode
[id=6f3d624b-a7dd-46e1-b229-db8a85cf8ece,
consistentId=c67390a7-9746-445b-9f40-b98ea32cc1ed, addrs=ArrayList
[10.135.34.67, 127.0.0.1], sockAddrs=HashSet [/10.135.34.67:47500,
/127.0.0.1:47500], discPort=47500, order=13, intOrder=9,
lastExchangeTime=1704713028652, loc=false, ver=2.14.0#20220929-sha1:951e8deb,
isClient=false], msg=GridIoMessage [plc=10, topic=TOPIC_QUERY, topicOrd=19,
ordered=false, timeout=0, skipOnTimeout=false, msg=GridQueryCancelRequest
[qryReqId=33]]]
org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed to
send message (node left topology): TcpDiscoveryNode
[id=6f3d624b-a7dd-46e1-b229-db8a85cf8ece,
consistentId=c67390a7-9746-445b-9f40-b98ea32cc1ed, addrs=ArrayList
[10.135.34.67, 127.0.0.1], sockAddrs=HashSet [/10.135.34.67:47500,
/127.0.0.1:47500], discPort=47500, order=13, intOrder=9,
lastExchangeTime=1704713028652, loc=false, ver=2.14.0#20220929-sha1:951e8deb,
isClient=false]
{noformat}
is it normal ?
> 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)
