-
Notifications
You must be signed in to change notification settings - Fork 342
502 causes stack restart #1033
Replies: 2 comments · 1 reply
-
@jim-counter Thanks for report this issue, a couple questions for this issue:
Basing on the provided log, the failed transaction make the coordinator restart which is a feature other than a bug, we need to make sure the service can keep running even got crash issue. However, this failed issue should be handled properly, will have an investigation for it. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi, at the time I saw this I was running Query node output. Polkadot
It does look like something made the node unhappy around 2022-05-17T01:48:26.201Z
Kusama
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Happened again yesterday.
|
Beta Was this translation helpful? Give feedback.
-
I've noticed this happen a few times:
It looks like a 502 when calling
eth_getTransactionByHash
causes a restart.I also noticed that my project nodes were not happy afterwards (complaining of errors). A restart of the whole stack seemed to fix everything.
Is this by design? Is there scope to add a retry mechanism or is that dangerous in this scenario?
Beta Was this translation helpful? Give feedback.
All reactions